Email & password login
FreeFlow@rabbinatix/email-password-login by Rabbinatixupdated Sep 30, 2026
A client signs in with an identifier and password; the auth service checks the user store and issues a token.
The classic sign-in flow, ready to fit your systems:
- Client app validates the form and calls the login API.
- Auth service validates the request, finds the user, compares the password hash and returns a token.
- User store answers the lookup. Event bus (optional) receives
user.logged_in.
Invalid credentials never reveal whether the account exists: a wrong password and an unknown user both get the same 401.
The Sign in and Welcome screens come with it on the client app, as a design to click through: Sign in opens Welcome.
Previewlanes are roles; you pick your systems when importing
- No matches
FalseNot found401Other
Start in Client app. step 1 of 16. key stepOn Submit login form
Call to another system in Client app. step 2 of 16. key stepCall sign in
Start in Auth service. step 3 of 16. key stepOn POST /api/v1/login
Resource in Auth service. step 4 of 16. key stepFind user
Answer in User store. step 5 of 16. key stepusers.findByIdentifier
Step in Auth service. step 6 of 16. key stepValidate credentials
Resource in Auth service. step 7 of 16Publish user.logged_in
Answer in Event bus. step 8 of 16. key stepuser.logged_in
Return in Auth service. step 9 of 16. key stepReturn 200
Return in Auth service. step 10 of 16. key stepWrong password → 401
Return in Auth service. step 11 of 16. key stepUnknown user → 401
Return in Auth service. step 12 of 16. key stepInvalid request → 401
Return in Client app. step 13 of 16. key stepReturn
Return in Client app. step 14 of 16. key stepReturn
Return in Client app. step 15 of 16. key stepReturn
Return in Client app. step 16 of 16. key stepReturn
Client app
Web frontend
Auth service
Backend service
User store
Database
Event bus
Queue / event bus
Up and down arrows: previous or next step. Home, End: first or last. Enter: select. Shift F10: more actions.
APIs
POST{base}/login· Sign in with an identifier and password
Auth service provides it · Client app calls it
Request body
email: string password: string
200
accessToken: string refreshToken: string expiresIn: integer tokenType: enum(Bearer)
401
error: string
Data operations
users.findByIdentifierqueryon User store(email: string)
user.logged_inpublishon Event bus(userId: integer)
Test cases
Valid credentials→ Login succeeds
Wrong password→ Invalid credentials
Unknown identifier→ Invalid credentials
Missing identifier→ Missing field
Missing password→ Missing field
Login publishes user.logged_in→ Login succeedswith “Publish user.logged_in”
Requirements
Reject invalid credentials without revealing whether the account exists.
The identifier and password are required to sign in.
Roles (4)
Client app
Where the user types the identifier and password · Web frontend or mobile app
Auth service
Checks credentials and issues tokens · Backend service
User store
Database with the user records · Database
Event bus (optional)
Receives user.logged_in (optional) · Queue / event bus
Settings
Token lifetime (seconds)3600
Token typeBearer
Publish user.logged_inon
Login identifier fieldemail (renamable)
Also as a whiteboard
Versions
