3 min read Updated October 2026
OpenID Connect Discovery & Standard Endpoints
Standard RFC OpenID configuration, public JWKS endpoint, and OAuth 2.1 protocol endpoints.
#Standard OIDC & OAuth Protocol Endpoints
NSGO implements standard OpenID Connect Core 1.0 discovery endpoints:
#Public JWKS Key Verification (/.well-known/jwks.json)
NSGO exposes active public RSA keys via RFC 7517 JWKS format. Client applications and reverse proxies cache these public keys to verify RS256 token signatures locally without roundtripping every request to the NSGO database.
Private RSA keys are cryptographically guarded in Supabase secure vault functions and never exposed over HTTP.
Was this documentation page helpful?
Related Documentation
Using the Drop-In NSGO Auth SDK (@/lib/nsgo-auth)
Integrating downstream TypeScript applications with the NsgoOAuthClient client library.
Read Article
Central Developer Portal on Main Website
Centralized engineering documentation, architecture diagrams, and ecosystem API references on naborajs.me/docs.
Read Article
Ecosystem SSO & OAuth 2.1 Architecture
How downstream applications authenticate with NSGO using OAuth 2.1 and PKCE S256.
Read Article