OIDC discovery
OIDC-compatible clients can discover the provider configuration here.
https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/.well-known/openid-configuration
TECHNOVA IDENTITY PLATFORM
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
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-compatible clients can discover the provider configuration here.
https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/.well-known/openid-configuration
Use this as the TechNova identity issuer.
https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1
https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/oauth/authorize
https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/oauth/token
https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/oauth/userinfo
https://maxlbgiomkdfynnjoghs.supabase.co/auth/v1/.well-known/jwks.json
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.
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