SSO Configuration
Configuration

SSO Configuration

Configure Single Sign-On for portal login via OIDC, GitHub OAuth, or AWS OIDC.

Using an AI assistant? Give it this file.

/llms.md is a single Markdown file covering installation, configuration, quickstart, clients, upstreams, permissions, TLS, and production deployment. Copy it and paste it into your AI chat, or tell the AI to fetch https://drevnix.tech/llms.md.

SSO Configuration

Drevnix supports Single Sign-On for portal login, letting your team authenticate with your existing identity provider instead of managing separate Drevnix passwords.

SSO is configured through the Settings page and takes effect immediately. No restart required. SSO availability is controlled by your license.

Supported providers

ProviderType
Any OIDC-compliant IdP (Okta, Keycloak, Auth0, Ping, etc.)Generic OIDC
GitHubGitHub OAuth
AWSAWS OIDC

You can configure multiple SSO providers simultaneously.

Generic OIDC

Works with any standards-compliant OpenID Connect identity provider.

Required fields:

FieldDescription
Issuer URLYour IdP’s OIDC discovery URL (e.g. https://accounts.google.com or https://your-okta-domain.okta.com)
Client IDThe OAuth client ID from your IdP
Client SecretThe OAuth client secret from your IdP

Setup steps:

  1. Create an OAuth/OIDC application in your identity provider
  2. Set the redirect/callback URL to: https://drevnix.company.com:8001/auth/oidc/callback
  3. Copy the client ID, client secret, and issuer URL
  4. In Drevnix, go to Settings → SSO → Add OIDC Provider
  5. Paste the values and click Save

GitHub OAuth

Lets portal users log in with their GitHub account.

Required fields:

FieldDescription
Client IDFrom your GitHub OAuth App settings
Client SecretFrom your GitHub OAuth App settings

Setup steps:

  1. Go to GitHub Developer Settings → OAuth Apps and create a new app
  2. Set the Authorization callback URL to: https://drevnix.company.com:8001/auth/github/callback
  3. Copy the client ID and generate a client secret
  4. In Drevnix, go to Settings → SSO → Add GitHub Provider
  5. Paste the values and click Save

AWS OIDC

For teams using AWS-issued OIDC tokens (e.g. from IAM Identity Center or EC2 instance metadata).

Required fields:

FieldDescription
Client IDAWS OIDC client ID
Client SecretAWS OIDC client secret
Issuer URLAWS OIDC issuer endpoint

Permissions for SSO users

SSO users are treated as portal users once authenticated. On first login, a portal user account is created for them automatically with no extra permissions beyond the defaults. A super-admin must grant additional permissions (such as audit-logs:view or api:access) to SSO users just like any other portal user.

Disabling SSO

Remove a provider from Settings → SSO and click Save. Portal users who previously logged in via SSO will need to use a password instead. Reset their passwords via Users → Set New Password before disabling.