SAML 2.0 (Including InCommon, ADFS, Shibboleth, and other SAML-compatible IdPs)

Screenshot 2023-07-24 at 11.53.09 AM.png

Involve supports Single Sign On (SSO) via SAML 2.0. A number of Identity Providers support the SAML 2.0 standard and can be configured to be used with Involve. Please consult your IdP documentation for how to complete the configuration for a new Service Provider.

SAML 2.0

To configure SAML, we’ll need the following:

  • Metadata URL
  • Logout URI (optional)
  • Service should return the NameID as an email address. This should be an email address that matches a user record in your data upload
    • Email address is the only required claim. The name for this claim does not matter
  • A user account and password for testing
    • If test account is not provided, configuration could be delayed 30 to 60 days.

We provide:

We require:

  • SHA-256 as your signing algorithm
  • Your signing certificate to be signed by a commercial certificate authority
Note: Involve is not a member of the InCommon federation, but supports SSO via InCommon using your EntityID. Involve will need to be configured as a service provider/application in your IdP.
Note: At this time, Involve does not support IdP-initiated SSO. In order to log in to Involve, a user will need to directly visit the application.
Note: Please allow 30 days for SSO configuration
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.