Set up Better Auth
Select Better Auth when you install Noxus. You cannot switch an existing installation by changing this setting: use the migration guide.- VM installer
- Helm
auth_backend: better-auth in the installer YAML. The installer generates the required secrets.Create the first administrator
On a new self-hosted installation, opening Noxus takes you to Setup:- Find the one-time setup token in the frontend logs, in the block
[auth-setup] INSTALLATION SETUP REQUIRED. - Enter the token, your name, email and a password.
- Complete onboarding. This account becomes the platform administrator.
Authentication email
Noxus sends verification, password reset and password setup emails. By default, Noxus email sends these from a Noxus address, with no setup required. Your installation needs a valid license and access to Noxus Central Services. To send from your own domain, open Settings → Integrations, choose Server email, then choose a SendGrid or SMTP connection under Send with and a From address. If you turn email off, users cannot sign up with a password or reset it.Add login methods
Open Settings → Identity & access → Authentication → Add connection. Each method shows what to enter in the provider: a redirect URI, or for SAML a Noxus metadata URL. Changes apply immediately.
For OpenID Connect, set the optional Email domains to restrict new signups to those domains. Add one chip per domain, or paste a comma-separated list. This does not prevent existing linked or imported users from signing in. Noxus trusts the email supplied by your identity provider unless the provider marks it unverified.
For Microsoft Entra OIDC connections, users without a mailbox address may sign in with their user principal name (for example,
[email protected]). Use that address for invitations and domain restrictions. Other OIDC providers must supply an email for new users to sign up.
Existing users add a new login method to their account in Settings → User → Profile → Connected sign-in accounts. The new login must use the same email.
GitHub sign-in is not available with Better Auth. For SAML, only login started from Noxus is supported (not from the IdP portal), and Single Logout is not supported.
Access and security settings
In Settings → Identity & access, administrators can:- Restrict which email domains or email pattern can create an account (Access & security → Access control).
- Add new users to this organization automatically (Advanced → Signup policy → Join this organization).
- Brand the login page with an application name and logo (Authentication → Login branding).
- Map SAML attributes or OpenID Connect and Microsoft claims (for example
groups) to workspaces and roles (Advanced → Workspaces and Roles mapping).
Attribute mapping
Enable attribute mapping can be turned on once at least one sign-in connection is enabled. Rules read the SAML attributes, or the claims in the ID token, of the sign-in that started the user’s session. Only text values and lists of text are used.- Users who are already signed in must sign out and in again before their claims are available to the rules.
- Microsoft Entra sends the
groupsclaim only when the app registration is configured to emit it (Token configuration → Add groups claim), and sends group object IDs, not names. For users in more than 200 groups Entra leaves the claim out. Assign app roles and match on therolesclaim in that case. - OpenID Connect connections added in settings request the
openid,profileandemailscopes. Claims that need another scope are not available.
Migrate from Auth0
Move an existing installation to Better Auth.
Authorization
Manage permissions after a user signs in.