As a user, I want separate login and registration pages so that I can securely sign in or create an account, with email validation and a minimum password length of 8 characters.
Acceptance Criteria
Separate endpoints are provided:
POST /login for authentication.
POST /register for new user creation.
Email input must be validated using a standard email regular expression.
Password must be at least 8 characters; validation enforced on registration.
Registration requires confirmation of password; both must match.
On successful registration, the user record is stored in the database with a hashed password (e.g., bcrypt).
Duplicate email addresses are rejected with an appropriate error message.
Invalid email format or short password returns a clear error response to the client.
Successful login creates a session or returns a JWT token (implementation detail, but must indicate authentication success).
After login, the user is redirected to the job creation flow or dashboard.
Authentication flows integrate with the frontend scaffold (/web application) using the appropriate API endpoints.
No additional business rules (e.g., email verification) are required per clarification.
## User Story
As a user, I want separate login and registration pages so that I can securely sign in or create an account, with email validation and a minimum password length of 8 characters.
## Acceptance Criteria
- Separate endpoints are provided:
- POST /login for authentication.
- POST /register for new user creation.
- Email input must be validated using a standard email regular expression.
- Password must be at least 8 characters; validation enforced on registration.
- Registration requires confirmation of password; both must match.
- On successful registration, the user record is stored in the database with a hashed password (e.g., bcrypt).
- Duplicate email addresses are rejected with an appropriate error message.
- Invalid email format or short password returns a clear error response to the client.
- Successful login creates a session or returns a JWT token (implementation detail, but must indicate authentication success).
- After login, the user is redirected to the job creation flow or dashboard.
- Authentication flows integrate with the frontend scaffold (/web application) using the appropriate API endpoints.
- No additional business rules (e.g., email verification) are required per clarification.
marko
added this to the (deleted) project 2026-05-24 05:25:50 +00:00
marko
changed title from user auth to User Authentication – Separate Login and Register Pages2026-05-24 05:57:25 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
User Story
As a user, I want separate login and registration pages so that I can securely sign in or create an account, with email validation and a minimum password length of 8 characters.
Acceptance Criteria
user authto User Authentication – Separate Login and Register Pagesmarko referenced this issue2026-05-24 07:16:36 +00:00
reid referenced this issue2026-05-26 06:21:13 +00:00
reid referenced this issue2026-05-26 16:11:34 +00:00
reid referenced this issue2026-05-26 16:25:44 +00:00
reid referenced this issue2026-05-26 17:11:00 +00:00
marko referenced this issue2026-05-29 00:14:29 +00:00