- Task
- Version · 6.0.2
- Manage
Manage authentication settings
Last updated: November 17, 2026
Decide whether people can create their own accounts, confirm the server can send emails, and see how your users can sign in.
Before you begin
You need the Manage workspace settings permission, which members of the Administrators group have. Anyone else who opens the page sees a message that they do not have access.
Procedure
Open the Authentication page
In Liquibase Secure server, go to Administer > Authentication. The settings on this page apply to every workspace on the installation.
(Optional) Close or open self-service registration
Self-service registration lets anyone who reaches the installation create an account, with an email address and password or with a Google, GitHub or Microsoft sign-in. It is on by default. Turn it off when the server's address can be found publicly, such as a demo or test environment.
To change it, use the switch on the Self-service registration card. The badge below the switch changes to Enabled or Disabled, and a message confirms the change.
When registration is closed:
The Create one link on the sign-in page is hidden, and the server rejects registration requests, so the setting cannot be bypassed through the API.
Someone who opens the create-account page directly sees Sign-up is closed, with a message to ask an administrator for an invitation or to sign in with single sign-on.
New accounts through Google, GitHub or Microsoft sign-in are refused. Accounts already linked to one of them still sign in.
Closing registration does not change:
Password sign-in for existing accounts, including the first administrator.
Invitations. An invited user can still create an account. See Invite and manage users.
Microsoft Entra single sign-on. A new user who signs in through it still gets an account and lands in the Pending group. See Signing in with single sign-on.
Until someone changes the switch, the installation follows LIQUIBASE_PLATFORM_SELF_SERVICE_REGISTRATION_ENABLED in the deployment's .env file, and the card says so. Once you change the switch, the setting on this page overrides that variable, and the card shows the variable's value as the deployment's default.
Check email delivery
The Email delivery card shows whether the server can send emails, which it uses for password resets, invitations and address verification. The badge reads Configured or Not configured. It reads Checking… while the page loads.
The card shows status only. You can turn emails on or off in the deployment's .env file, not on this page.
When email is not configured, those emails are not sent, and password sign-in still works. The card lists the steps to turn it on:
Set
LIQUIBASE_PLATFORM_SMTP_HOST,LIQUIBASE_PLATFORM_SMTP_PORTandLIQUIBASE_PLATFORM_SMTP_FROMin the deployment's.envfile. Also setLIQUIBASE_PLATFORM_SMTP_USER,LIQUIBASE_PLATFORM_SMTP_PASSandLIQUIBASE_PLATFORM_SMTP_SECUREif your mail server needs them.Run
./liquibase-platform start, which recreates the API with the new settings.
Until email works, a user who forgets their password cannot get a reset email. An administrator can create a one-time reset link instead, valid for one hour. Run this command on the Docker host, from the deployment directory, or add --dir with the path to that directory:
Be sure to replace your_user_email with the address of the account, for example priya.shah@example.com.
./liquibase-platform reset-password your_user_emailReview sign-in methods
The Sign-in methods on this instance card summarizes how people can sign in:
Email & password login is always Active.
Microsoft Entra SSO shows one of these statuses:
Not configured: No provider is set up.
Disabled: A provider is set up but turned off.
Enabled: A provider is set up and turned on.
Checking…: The status is still loading.
Unavailable: The status could not be fetched.
This card shows status only. To set up or turn on SSO, go to Administer > Single Sign-On and follow Configure single sign-on with Microsoft Entra.
Self-service registration matches the setting chosen in step 2.
Every change on this page is recorded in the system log. See Review the system log.