Authentication Should Be Fully Prompt-Driven
After reviewing the current implementation, I noticed that the Sign-In Method still requires developers or administrators to manually select or configure authentication options before the login system becomes functional.
From an enterprise software architecture perspective, this is not the expected behavior.
Since the entire application is being generated through AI-defined prompts, the authentication workflow should also be generated automatically based on those prompts.
For example, if the prompt specifies:
- An Admin Login page with predefined credentials.
- A Staff Login portal where credentials are assigned by the Administrator.
- A Customer Registration page where users create their own username and password.
- A Sub-Admin login with predefined roles and permissions.
Then the system should automatically generate the complete authentication architecture accordingly.
There should be no requirement to manually select a Sign-In Method or manually configure authentication settings after the application has been generated.
The AI prompt should define:
- Authentication type
- Login pages
- User roles
- User provisioning logic
- Credential generation
- Password policies
- Role-based permissions
- Authentication workflows
Based on these prompt definitions, the system should automatically create the required database structures, authentication services, identity records, and server-side configuration.
The authentication engine should simply verify the credentials that have already been created automatically by the application’s business logic.
In other words, authentication should be prompt-driven, not manually configured after software generation.
The desired workflow should be:
AI Prompt
│
▼
Generate Software Architecture
│
▼
Generate Authentication Configuration
│
▼
Create Database Schema
│
▼
Create Default Users (if defined)
│
▼
Configure Roles & Permissions
│
▼
Deploy Application
│
▼
Users Can Sign In Immediately
At no stage should a developer or administrator be required to manually configure authentication options through the Sign-In Method page if those requirements have already been defined in the AI prompt.
This is the expected behavior for an AI-driven application generation platform and aligns with modern enterprise software development practices.
Thank you
Nabab
