SSO for your Proof account lets you and all your teammates log into Proof using the credentials stored in your organization's SAML Identity Provider (IdP). Examples of IdPs include ActiveDirectory, Auth0, Google, and Okta. With SSO, account and credential management are not handled by Proof, but instead by your IdP.
- Users in your organization can log into Proof without needing to enter their password every time.
- SSO is compatible with parent/child org structures, allowing you to propagate certain teams/groups to a respective child org upon SSO login.
- Streamline new user onboarding with just-in-time user provisioning (JIT provisioning). Users will be created and updated automatically when they log in through SSO, allowing you to scale your operation with Proof faster.
- Once SSO is configured, users' former Proof account passwords will no longer work, unless they are organization admins.
- Users' former Proof account usernames will no longer work if those usernames do not match existing usernames in your organization’s IDP.
- This documentation assumes that you already have a SAML Identity Provider (IdP). If you do not have a SAML IdP, you can use any IdP that supports SAML 2.0 such as ActiveDirectory, Auth0, Google, and Okta.
- This documentation assumes you are on a "Pro" pricing tier. See our pricing page for more details.
To configure SSO on your Proof account, you'll need to provide Proof with the following information from your IdP:
- Entity ID
- Target URL
- X509 client certificate
You can enter these parameters individually, or provide a metadata file or metadata URL.
An organization admin can enable SSO and enter this information in Settings >> Team Security:
The IdP needs to be configured with the following Proof SAML data:
- Entity (or Issuer) ID: https://api.proof.com/saml/consume
- Assertion Consumer Service (ACS) URL: https://api.proof.com/saml/consume
- SP metadata URL: https://api.proof.com/saml/metadata
- Also available as a file
The IdP test environment needs to be configured with the following Proof SAML data:
- Entity (or Issuer) ID: https://api.fairfax.proof.com/saml/consume
- Assertion Consumer Service (ACS) URL: https://api.fairfax.proof.com/saml/consume
- SP metadata URL: https://api.fairfax.proof.com/saml/metadata
- Also available as a file
These attributes are sent from the IdP to Proof, in order to provision accounts on-the-fly, assign specific roles (e.g. admin vs. team member), and create users in child organizations.
Keep in mind the following required attributes:
Read more about the available SAML attributes below:
|Attribute Name||Attribute key case||Attribute value case||Attribute Description|
|case sensitive||case sensitive||A unique, immutable identifier for the user. Can be an ID number, email address, username, etc.|
|case insensitive, with/without ||case sensitive||User's first name|
|case insensitive, with/without ||case sensitive||User's middle name. Strongly reccomended if your organization users will be signing documents in a notarization transaction.|
|case insensitive, with/without ||case sensitive||User's last name|
|case sensitive||case sensitive||User’s full name, e.g. “John Patrick Smith Jr.”|
|case insensitive||case insensitive||User's email address|
|case sensitive||case insensitive||An array of strings designating the user's roles. Choose any subset of the following:|
If omitted, the default role of
|case sensitive||case sensitive||A Proof organization ID. If specified, the user will be added to this org, otherwise they'll be added to the org where SSO was configured. Use this attribute if you'd like to sign a user into a specific child org.|
|case sensitive||case insensitive||The notary’s state of operation, as an abbreviation.|
|case sensitive||case insensitive||An array of strings representing languages spoken by the user (notary). Supported values are |
Updated 1 day ago