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 Location, XML File URL:
- Metadata must be hosted by the campus
- Entity ID:
- Federated Login URL (Optional):
- Federated Logout URL (Optional):
- Federated Validation URL (Optional):
- Identity Attribute:
- Identity Attribute: The claim should provide an email during sign-in which matches one uploaded in the school’s datafile
We provide:
- Our Entity ID: https://auth.presence.io/AuthServices
- Assertion Consumer Service Endpoint (Reply URL): will be provided by your Implementation Coordinator
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.
Comments
Please sign in to leave a comment.