Developer demo · No account needed

Try the integration

Run a real OpenID Connect sign-in against a live Thoryn tenant. You sign in on the hosted login, Thoryn returns an authorization code, and this app exchanges it for tokens on the server using PKCE. The page then shows the decoded ID-token claims.

Start the sign-in round-trip

The access token and ID token never reach browser JavaScript. The PKCE verifier is held in an httpOnly cookie and the code-for-token exchange runs server-side.

What runs under the hood

1. Authorization request. The server generates a PKCE code_verifier and its S256 code_challenge, then redirects you to the tenant's authorize endpoint.
2. Hosted login. You authenticate on the tenant's own login screen. Thoryn redirects back with a one-time authorization code.
3. Token exchange. The server posts the code plus the code_verifier to the token endpoint and receives an ID token and access token.
4. Claims. The server decodes the ID token and renders its claims.

Issuer: https://demo.hub.stg.thoryn.org
Client: demo-rp
Scope: openid profile