Before you begin, make sure you have an Admin account (Viewer or Contributor) with Abstract.
Abstract supports SAML 2.0 protocol. If your IdP uses the SAML 2.0 protocol, you may be able to configure SSO in Abstract.
You may need to add the following information to your IdP:
|Abstract’s Assertion Consumer Service (ACS) URL||https://auth.goabstract.com/saml/response|
About SAML responses:
- We currently only support HTTP:POST binding.
- We are expecting an “email” Assertion Attribute, as shown below.
<saml2:Attribute Name="email" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified"> <saml2:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">email@example.com</saml2:AttributeValue> </saml2:Attribute>
- Open the Abstract web app.
- Go to the Permissions page in the left side bar.
- In the Configure SSO section, enter your Metadata URL and Entity ID.
- Enter any manual exceptions you might have. Emails listed in the manual exceptions section will bypass SSO and be able to log in with email and password.
- Note: You’ll need to use primary email addresses in the manual exceptions list. SSO activation will fail if the email you list is a user’s secondary email. If that happens, you’ll see an error message with the primary email for the failing account. Add that primary email to the manual exceptions list after you’ve verified you know the user.
- Click Test with my Account. If the test fails, you’ll need to contact our support team to manually enable SSO.
- Toggle Activate SSO on.
- Click Save Changes.