Skip to content
English
  • There are no suggestions because the search field is empty.

Enforcing single sign-on and managing providers

Test your single sign-on set up, require it for everyone on a mapped domain, and edit, disable or delete a provider later.

Test your single sign-on set up, require it for everyone on a mapped domain, and edit, disable or delete a provider later.

This is for System Admins. You need an identity provider and at least one email domain already set up under Settings then Security: see "Setting up single sign-on".

Test before you enforce

There is no test button. Test by signing in.

  1. Open a private browser window and go to the Recruit sign-in page.
  2. Enter the work email of a user who already exists in Recruit and whose domain you mapped, then select Continue.
  3. Check that Continue with and your display name appears, select it, and complete the sign-in at your provider.
  4. You should land in Recruit signed in as that user.

Do this with at least one person other than yourself, ideally with a different role, before enforcing.

Enforce single sign-on

The Enforce single sign-on card has one switch: Require single sign-on for all users. When it is on, password sign-in is disabled for people whose email domain is mapped to a provider. A password attempt returns "You must sign in with single sign-on". You will see "SSO enforcement updated." when the change saves.

Plan for these consequences:

  • Enforcement follows the domain mapping. People whose domain is not mapped can still use a password, so an unmapped contractor domain is not locked out.
  • It applies to you as well. Enforcing before the provider works can lock every mapped user out, including administrators. Keep the switch off until a colleague has signed in successfully.
  • If enforcement is on and the provider is disabled, mapped users see "Your organisation requires single sign-on, but no provider is configured. Contact your administrator." and cannot sign in until you enable a provider or turn enforcement off.
  • Turning the switch off puts password sign-in straight back.

Edit, disable or remove a provider

  • Edit: select the pencil icon. You can change the display name, issuer URL and client ID. Leave Client secret blank to keep the existing secret, or type a new one to replace it, for example when the secret in your provider expires. Select Save.
  • Disable or enable: select Disable on the provider row, and Enable to switch it back on. A disabled provider is never offered at sign-in, though its domain mappings stay in place.
  • Delete: select the bin icon and confirm with Delete provider. Users routed to it can no longer sign in with SSO. Turn enforcement off first if those users would otherwise be left with no way in.

How users are matched

Recruit matches the person by email address. The person must already exist as a user in Recruit, added through Settings then Users. A successful sign-in at your provider for an email that has no Recruit user is refused, and nothing is created. Role and access are always the ones set in Recruit.

Removing someone from your identity provider stops their next SSO sign-in. It does not end a session they already have open, so also remove their access in Recruit when someone leaves.

If people report an error at sign-in, see "Fixing single sign-on sign-in errors".