✦ TECHNOVA

TECHNOVA IDENTITY PLATFORM

Continue with TechNova

TechNova can act as an OAuth 2.1 and OpenID Connect identity provider. Registered applications can let their users sign in with an existing TechNova account using Authorization Code + PKCE.

DEVELOPER CONSOLE

Create your own Continue with TechNova app

Sign in with your TechNova account, register an OAuth application, add exact redirect URLs and get a Client ID. Public browser/mobile apps use PKCE and confidential server-side apps receive a Client Secret that is only shown when created or regenerated.

OIDC discovery

OIDC-compatible clients can discover the provider configuration here.

https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/.well-known/openid-configuration

Issuer

Use this as the TechNova identity issuer.

https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1

Authorization endpoint

https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/oauth/authorize

Token endpoint

https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/oauth/token

UserInfo endpoint

https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/oauth/userinfo

JWKS endpoint

https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/.well-known/jwks.json

Supported identity scopes

openid profile email

Each client application needs its own registered Client ID and exact redirect URI. Public browser and mobile clients should use PKCE with the S256 challenge method.

Quick start

Send users to the TechNova authorization endpoint with your Client ID, exact redirect URI, requested scopes, state and an S256 PKCE challenge. After the user approves access, exchange the returned authorization code at the token endpoint.

scope=openid profile email response_type=code code_challenge_method=S256
Never place a confidential Client Secret in browser JavaScript or a public repository. Public clients do not receive a secret and should always use PKCE.
Developer Console My TechNova account Manage authorised apps