Introduction

Currently, 12Twenty offers three options for single sign-on integration with your system -- SAML, CAS, and 12twenty Proprietary. Your account management point of contact will put you in touch with one of our technical experts to coordinate the SSO integration between systems.

SAML

In the past, 12Twenty has done SAML integrations with the following products:

Integration with other SAML based products may require extra service fees. To move forward with the SSO SAML integration with 12Twenty, we will need a few things from you:

ItemDetails
SAML EntityIDIf you are a part of InCommon, we will use this to look up your metadata and connect
SAML IdP MetadataIf you are a not part of InCommon, we will use this to connect instead of the above
SAML AttributesThe SAML attribute(s) to be released to us (e.g. email address or student id) to match up students between systems. We prefer eduPersonPrincipalName (EPPN), urn:oid:1.3.6.1.4.1.5923.1.1.1.6, which is often an email address or student id.
Dummy AccountWe will use this on our side to continuously test and monitor the SSO integration between our systems
Sample ResponseThis will help us associate the authenticated user to the correct record in our systems. Please include the student identifier in the response.


InCommon Members

If you are a member of InCommon, you can look us up by our EntityID's based for our two environments.

EnvironmentEntityID
Productionhttps://sp.12twenty.com/shibboleth
Stagehttps://sp.stage-12twenty.com/shibboleth

Non-InCommon Members

If you are not a member of InCommon, no problem! You can find our metadata in the following locations.

EnvironmentMetadata Location
Productionhttps://sp.12twenty.com/Shibboleth.sso/Metadata
Stagehttps://sp.stage-12twenty.com/Shibboleth.sso/Metadata

CAS

To move forward with the SSO CAS integration with 12Twenty, we will need a few things from you:

ItemDetails
Login UrlThe location where the user will be redirected to when attempting to access 12Twenty
ServiceValidate UrlThe service that checks the validity of a service ticket and returns an XML-fragment response
logout UrlThe location that will successfully log out the user from both systems
User Identifier ExamplesThis is the unique id of the user that will allow the correlation of users between systems.
Examples: homer732, bart.simpson@school.edu
Dummy AccountWe will use this on our side to continuously test and monitor SSO integration between systems

12Twenty

Available by request. Please contact us.