Varqeni Help

Single sign-on

Updated 11 November 2026

An admin sets up a provider in Administration, Authentication. Your installation decides whether the console signs people in itself or a sign-in proxy in front of it does.

AvailabilityFor the person who runs Varqeni for your team. In early access that is usually Fortis, working with you.

Steps

  • Register Varqeni with your provider: open the provider's card, copy the redirect URI it shows, and create a web application at your provider with it.
  • Copy the client ID and secret: paste them into the provider's page in Varqeni. The secret is encrypted on the Varqeni host and never shown again.
  • Choose who may sign in: allowed email domains (required for Google), which claim is the sign-in name, which claim lists groups, and the role for someone signing in for the first time.
  • Test, then turn it on: Test checks that Varqeni can reach the provider. Turn on Enabled to show Sign in with ... on the sign-in page.
  • Teams from groups: a team in Users and access that names a group gets everyone your provider puts in it.

What you should see: Single sign-on signs people in only when your installation sets the sign-in mode to single sign-on, so a mistake on this page can never lock anyone out. SAML and SCIM are not available yet.

What it can and cannot do

Can

  • Let people sign in with Microsoft Entra ID, Okta, Google, GitLab or any OpenID Connect provider.
  • Give teams their members from your provider's groups.

Cannot

  • Show the client secret again after it is saved. Paste a new one to change it.

Still stuck? Contact support or email info@fortisdatagroup.com.