Overview
Federation allows enterprise users to authenticate with NxtSight using their existing corporate identity provider (IdP) — no separate NxtSight password required. NxtSight Identity supports SAML 2.0 and OpenID Connect (OIDC) protocols. Users authenticate at the IdP and receive NxtSight tokens mapped from their IdP attributes, inheriting project membership and roles through attribute mapping rules.Federation Architecture
SAML 2.0 Setup
Register NxtSight as SP in your IdP
Provide your IdP with the NxtSight SAML SP metadata URL:Configure the IdP to send the following SAML attributes:
ADFS_LOGINormail— the user’s login namememberOf— group membership for role mapping
Create attribute mapping rules
Mapping rules translate IdP attributes into NxtSight group memberships:
mapping-rules.json
Upload mapping rules
OpenID Connect Setup
Register NxtSight as OIDC client in your IdP
Register a new application in your OIDC provider (Keycloak, Azure AD, Okta):
- Redirect URI:
https://api.<your-domain>:5000/v3/OS-FEDERATION/identity_providers/<IDP_ID>/protocols/openid/auth/callback - Grant type: Authorization Code
- Scopes:
openid,profile,email,groups
Mapping Rule Reference
Next Steps
Authentication Backends
Compare federation with LDAP and SQL backend options.
Domain Management
Assign federation backends to specific organizational domains.
Security Hardening
Secure federation endpoints and enforce MFA for federated sessions.
Admin Troubleshooting
Debug SAML assertion errors and OIDC token mapping failures.