Works with Typestate. Built into Typestate.
OpenID Connect
Let people sign in with any OpenID Connect provider: Okta, Auth0, Keycloak, Zitadel, or a company's own.
Add sign-in with our Okta to my backend on Typestate
OpenID Connect is on, through set_sign_in.
A sign-in button for any provider that publishes an OpenID Connect address
Your key goes on the cockpit, never through me.
Ready on Sandbox after the next deploy.
What it does for a business
- A sign-in button for any provider that publishes an OpenID Connect address
- The platform reads the provider's addresses from that one address
- Admit only the addresses of one company, if you want
Reads
What an action of your backend reads from OpenID Connect.
ReadRead the signed-in personEvery action behind a sign-in knows who called it.
It takes nothing.
What it answers, for example
{
"email": "ada@example.com",
"id": "usr_41c"
}What it cannot do yet
- SAML is not built.
Add OpenID Connect to your backend
, and give it the provider's address. You paste the client id and secret on the cockpit.
Add sign-in with our Okta to my backend on TypestateOpen an accountMore sign-in and related integrations
Google
Let people sign in with their Google account.
Apple
Let people sign in with their Apple account.
Microsoft
Let people sign in with their Microsoft account from work, school or home.
Made by Typestate, and not by OpenID Connect. OpenID Connect does not endorse Typestate. OpenID Connect's own site