Before you start
- Each organization has one SAML connection.
- The identity provider must sign the SAML response, the assertion, or both. An unsigned response is refused.
- Sign-in starts at ProofAge (SP-initiated). A response your identity provider sends on its own (IdP-initiated sign-in) arrives without a request from ProofAge and is refused. A tile in your identity provider’s app dashboard works only if it opens ProofAge’s Sign-in URL.
- ProofAge does not provision users through SCIM and does not support Single Logout. Someone you remove in your identity provider can no longer sign in through it, but keeps a console session that is already open until it ends or is revoked, and keeps any other way in their account has (a password, a passkey, Google or Microsoft). Remove them from Team too. With Create accounts on first sign-in on, removing someone from Team alone is not enough: while they are still assigned to the app in your identity provider and their email is on a verified domain, their next single sign-on adds them back with the role for new members. Remove them in both places.
1. Verify your email domains
Under Settings → SSO, add the domain of your work email addresses, such asacme.com, and publish the TXT record the console shows at your DNS provider:
- Matching is exact:
eu.acme.comis a domain of its own and needs its own record. - Public mail domains such as
gmail.comoroutlook.comcannot be verified. - A domain can be verified by one organization only. If another organization has verified yours, contact support.
- Up to 10 domains per organization.
2. Create the connection
Choose Set up single sign-on. Nothing changes for your team until you enable it. The console shows four values to give your identity provider:
Copy them from the console; the connection ID is yours.
The sign-in URL for dashboard tiles
To let people start from a tile in your identity provider’s dashboard (Okta, Microsoft My Apps), point the tile at the Sign-in URL shown under Settings → SSO. Opening it starts a normal ProofAge sign-in and sends the person to your identity provider, which signs them straight in when they already have a session there. It works once the connection is enabled (step 6); before that, the sign-in page says “Single sign-on is not available for this organization.”3. Configure your identity provider
Create a SAML 2.0 application with the entity ID and ACS URL above, and set:- Name ID: a value that never changes for a person, in the persistent or email address format. A transient Name ID is refused: it differs at every sign-in, so ProofAge could never recognize the person again. ProofAge recognizes a person by the connection and the Name ID, never by the email address alone.
- Email: an attribute named
email,mail,emailaddressorhttp://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress. If none is sent, ProofAge uses the Name ID when its format is email address. A response without an email address is refused. - Name (optional, used for new accounts):
name,displaynameorhttp://schemas.xmlsoap.org/ws/2005/05/identity/claims/name, or a first and last name asgivennameandsurname(orsn).
4. Tell ProofAge about your identity provider
Under 2. Tell us about your identity provider, choose one way:- Metadata URL: the
httpsaddress of your identity provider’s metadata. ProofAge fetches it once, when you save. - Paste metadata XML.
- Enter manually: the identity provider’s entity ID, its sign-in URL (
httpsonly) and its signing certificate (PEM).
5. Accounts for new people (optional)
Create accounts on first sign-in lets someone on one of your verified domains sign in through your identity provider for the first time and join your organization:- a person with no ProofAge account gets one, without a password;
- a person who already has a ProofAge account but is not in your organization joins it.
6. Enable and test
- Choose Enable single sign-on. It is available once the identity provider is saved.
- Test it with your own account: in Profile → Security → Sign-in methods, choose Link single sign-on for your organization and sign in at your identity provider. Or, if your email is on a verified domain, sign out and use Sign in with SSO on the sign-in page.
- The Settings → SSO page then says “You have signed in through this connection.”
7. Require single sign-on (optional)
Under Settings → Security, Require single sign-on makes members whose email is on one of your verified domains sign in through your identity provider to work in your organization. Members on other addresses, such as contractors ongmail.com, are not affected.
ProofAge refuses to turn it on until:
- the connection is enabled;
- at least one domain is verified;
- you have signed in through the connection yourself (step 6), so you cannot lock yourself out.
Break-glass for administrators
Break-glass for administrators is on by default. While it is on, an administrator who signs in another way and proves a second factor (password with an authenticator code, a passkey, or Google or Microsoft with an authenticator code) can still open the organization, so an outage at your identity provider cannot lock you out. Turn it off only if you accept that risk.How your team signs in
On the sign-in page, Sign in with SSO asks for a work email and sends the person to your identity provider. It works for addresses on a verified domain of an organization whose connection is enabled; otherwise the page says “Single sign-on isn’t set up for this email domain.” The first time someone signs in through single sign-on, ProofAge finds their account like this:- They have signed in through this connection before (same Name ID): that account.
- Their email is on a verified domain:
- a member of your organization whose email address was verified is linked and signed in, and receives an email that single sign-on was added to their account;
- an account that is not a member joins your organization if Create accounts on first sign-in is on, and is refused otherwise;
- no account: created if Create accounts on first sign-in is on, refused otherwise.
- Their email is not on a verified domain: refused. A member links single sign-on from Profile → Security while signed in another way.
- does not ask for an authenticator code, and counts as signing in with two factors for Require two-factor authentication;
- works in your organization only. To open another organization they belong to, the person signs out and back in with their own account;
- asks for the person’s own password, passkey or provider before they add an authenticator app or a passkey or change their sign-in methods. An account created by single sign-on has none of these until the person sets a password with Forgot password? on the sign-in page;
- does not show the person’s sessions, devices or security activity, and cannot approve the MCP server or a connected app.
Turning it off
- Disable stops single sign-on at once and turns Require single sign-on off.
- Delete connection also removes everyone’s linked single sign-on and turns Require single sign-on off. Nobody loses their password or passkeys.
- The last verified domain cannot be removed while Require single sign-on is on.