Sign your colleagues in through your company's identity provider
SSO from the Team plan: link an OIDC or SAML provider, prove your domain with a DNS record, then choose the ways of signing in the organization admits.
With SSO (single sign-on), your colleagues sign in to Facteur with the account your company already gave them, with no extra password to remember. That account is held by your identity provider: the service of your company that confirms who is who, for example Microsoft Entra ID, Okta or Google Workspace.
You set SSO up yourself, from the application, with no quote and no call. It is included from the Team plan upwards. On a lower plan, the screen says so and names the plan you need.
Everything happens in Settings → Single sign-on. Owners and administrators manage the provider and the domains. Only the owner chooses the sign-in policy.
1. Link your identity provider
Click Link a provider, then choose the protocol. Your provider gives you the values asked for in its admin console, when you create an application for Facteur there.
- OIDC: three values to copy, the issuer (the https address of your provider, for
example
https://login.acme.com), the client ID and the client secret. Facteur keeps the secret encrypted and never shows it again. - SAML: the XML metadata file of your provider, which you paste or load with Load a metadata file. 512 KB at most.
Click Link. An organization has one provider.
SAML metadata is checked at once. It is refused, with the reason, if it names no sign-in address (HTTP-Redirect or HTTP-POST) or no signing certificate, if the certificate has expired or is not valid yet (the screen gives the date), if it signs with SHA-1, or if it contains a DOCTYPE.
The provider does nothing until a domain is proven. Without a proven domain after 7 days, it is deleted. The screen shows the date.
2. Prove your domain
The domain is the end of your colleagues' addresses: acme.com for paul@acme.com.
Proving it shows that the domain is yours. Without that proof, anybody could claim a
third party's domain and capture its sign-ins.
-
Click Declare a domain and write it as
acme.com, withouthttps://or a path. A subdomain, such aseu.acme.com, is declared separately. -
Facteur shows a DNS record of type TXT, with a copy button for its name and for its value:
_facteur-challenge.acme.com TXT facteur-verification=<token> -
Add that record at the host where you manage the domain name.
-
Click Verify. Facteur reads the record: if it is there, the domain is proven.
A new record can take a few minutes to propagate: try again if the first verification fails. The value is shown only once. If you lose it, click Get a new value: the old one no longer proves anything.
A domain already proven by another organization is refused.
Keep a way back in. Facteur refuses the proof if no owner has an address outside the domain. That owner is the one who can still open the organization if your identity provider goes down. If there is none, write to us from support to name an owner with another address, then prove the domain.
What changes once the domain is proven
- Your colleagues type their work address on the sign-in screen. The screen sends them to your identity provider on its own. Facteur adds no button.
- The password is refused to every address of the domain, including those whose account already has one, and yours if it is in the domain. Only an owner whose address is outside the domain keeps their password.
- A colleague who signs in through your provider for the first time joins the organization as a member. You do not have to invite them.
- An address that is not in a proven domain cannot get in through your provider.
So SSO is not added to the other ways in: for the addresses of the domain, it replaces them as soon as the domain is proven. Check your provider's configuration before you prove the domain.
Choose the ways of signing in the organization admits
The Sign-in policy section is reserved for the owner. Tick the ways of signing in the organization accepts: Password, Passkey, Social account, Company single sign-on. No box ticked: all are admitted. Click Save.
- A person signed in another way sees the organization greyed out, with the reason. The policy is read at every request: it applies at once, without waiting for a new sign-in.
- The owner always keeps access, whatever the policy. That is your way out on the day your identity provider is unavailable.
- To require SSO without a password, sign in through it once first. Otherwise the policy is refused: you could lock yourself out.
- Your members' other organizations are not affected.
Unticking the boxes goes back.
What changes for your members who work elsewhere
A session opened by your identity provider gives access to your organization, and to it alone. This holds for everyone, owners included.
If one of your members also belongs to another Facteur organization, for example a contractor who works for one of your clients, that organization appears greyed out to them, with the message "Your sign-in is limited to" followed by the name of yours. To go there, they sign out and sign in again without going through your provider.
Your provider decides who gets into your organization, so it decides only there. Without that limit, the administrator of your directory would get, by opening a session in the name of one of your employees, the access that employee holds at a third party.
Members who belong only to your organization see no difference. See Several organizations.
If your identity provider goes down
An owner whose address is outside the domain opens the organization with their password and their second factor.
Write to us as well from support: the Facteur team can reopen password sign-in on a proven domain, for 7 days at most. The screen then shows "Withdrawn until" followed by the date. Colleagues who never had a password create one with "Forgot password". On that date, sign-in through your provider resumes on its own.
Delete the provider
Click Delete beside the provider, then Delete the provider. Your colleagues can no longer sign in through SSO, and the declared domains go with the provider. Their Facteur accounts stay. Deleting is possible on any plan.
Known limits
- The screen does not give the return address to declare at your provider (the redirect URL in OIDC, the ACS URL in SAML). Ask support for it.
- A configuration the sign-in service refuses shows only when the first domain is proven. For example, a wrong or unreachable OIDC issuer makes the verification fail, and the domain stays unproven. To fix it, delete the provider and link it again: your domains will have to be declared and proven a second time.
- No automatic account synchronization (SCIM). A person removed from your directory can no longer sign in through SSO, but stays a member of the organization.
- The sign-in policy cannot require two-factor authentication. See Your organization.