Choose your stack
Pick the technology you're building with. Every guide uses your framework's standard OAuth 2.0 / OpenID Connect library — no NIA-specific SDK required — and points it at the same discovery URL.
JavaScript / Node.js
6 frameworksFrontend apps are public clients with PKCE in the browser; Node servers act as confidential clients.
Python
3 frameworksConfidential clients — the authorization code is exchanged server-side with your client secret.
Java
1 frameworkSpring Security ships a first-class OAuth2/OIDC client — point it at the NIA discovery URL.
Spring Boot
MediumRecommended library
Spring Security OAuth2 Client.NET
1 frameworkBuilt-in OpenID Connect middleware handles the whole flow from a few lines of configuration.
Go
1 frameworkCompose the standard oauth2 package with go-oidc for discovery and ID-token verification.
PHP
1 frameworkLaravel Socialite with an OIDC driver gives you a familiar provider callback.
Mobile
3 frameworksNative apps use the authorization-code + PKCE flow via the system browser (AppAuth).
Don't see your framework?
NIA is a standards-compliant OIDC provider — any conformant library works. Point it at the discovery URL and follow the generic OAuth 2.0 flow.
View endpoints