01
Sign-in
The application sends the user to Vorlaxen. After consent, the session opens with an authorization code.
Vorlaxen IdP
One sign-in. Every application uses the same door.
Sign-in is ready. The user enters with a Vorlaxen account, and the application sees only what it needs.
Identity layer
A product should not have to build its own front door.
What it does
Identity with a clear boundary.
02
Scopes
Profile, email, avatar, phone, and roles are requested separately. The application does not receive what it did not ask for.
03
Clients
Public and confidential clients stay distinct. Public clients must use PKCE.
04
Trust
Identity stays safe. From sign-in to sign-out, everything lives in one place.
Flow
Three steps.
01
Register the application
The client is defined with its allowed scopes and redirect addresses.
02
The user consents
Sign-in happens at Vorlaxen. The user sees what the application is asking for.
03
Identity is delivered
The application receives only the information it requested. The rest stays private.
Early access
Vorlaxen IdP is in early access.
It is not open to everyone yet. Get in touch for access and integration.