GetAccept supports single sign-on (SSO) logins through SAML 2.0 if you're on our Enterprise plans.
Before provisioning SAML, make sure you have the following:
- An installed Identity Provider (IdP) SSO system that supports SAML 2.0. Several SAML IdPs are available. If your organization's IdP supports SAML 2.0 you can configure SAML in GetAccept. Examples: Microsoft ADFS, Okta, OneLogin.
- X.509 certificate. This certificate is used to verify the signature in SAML assertions.
- Valid email address. An Email Attribute is required in the assertion: either the SAML Subject or another SAML attribute per the SAML configuration. The value of the Email Attribute must be a valid email address. It is used to uniquely identify the user in the entity/organization.
Setting Up GetAccept on Your Identity Provider
Your SAML IdP will need to know the GetAccept entity URL to which the SAML IdP should POST SAML assertions. In your IdP this might be called “Post Back URL,” “Recipient,” or “Destination,” among other names.
Keep in Mind
- GetAccept requires SAML 2.0.
- If you enable SAML authentication while you are logged into GetAccept make sure you have another session open with an alternate account login set up. Otherwise, you could lock yourself out of the app.