Register redirect URIs
The redirect URI must be an exact, server-approved value for your application. Never assume that any callback URL can be trusted just because it appears in a generated example.
DEVELOPERS / CONFIGURATION TOOLConfigure your
Configure your
sign-in integration.
Generate an SDK starter snippet using your own issuer and OIDC client registration. All values stay in your browser.
LOCAL CODE GENERATOR / NO BACKEND
◈
Preview mode. The code below is a configuration helper, not a client-registration portal or an active sign-in. Client IDs and callback URLs must be approved in the identity provider first. Do not enter secrets.
1. Application details
Local configuration: ready for preview.
2. Integration snippet
JAVASCRIPT / AUTHORIZATION CODE + PKCE
Generating…3. Register, test, launch
Run the shipped development identity server, register this client with the same redirect URLs, then integrate the SDK in your application. Before connecting live users, deploy a hardened production identity provider, configure the official issuer domain, and test token validation, consent, and sign-out end to end.
PLAYGROUND / READING THE OUTPUT
A snippet is the start, not the deployment.
The generator produces a client-side starting point; it cannot register a production OAuth client on its own.
Validate the response
The browser flow should use state and PKCE; OIDC authentication also requires nonce and validated ID-token claims. Production integrations must consider session expiry and logout propagation.
Secure the provider
A live identity service needs account recovery, consent and privacy information, audit trails, and incident handling. Treat local realm files as examples, not real deployment policy.
MAGNEXIS / FIELD GUIDEView Identity SDK reference