The blog is managed and hosted on GitHub. If you wish to update the contents of this post or if you have found an inaccuracy and wish to make corrections, we recommend that you please submit a pull request to this repository.
Paul Spaude of Unicon, Inc was kind enough to contribute this guide.
Rave is a mass notification system designed to deliver fast and effective messaging for routine and emergency communications. As a SAML2 service provider, Rave can be integrated with CAS running as a SAML identity provider and this blog post provides a quick walkthrough of how to make that integration possible.
Our starting position is based on the following:
- CAS
5.3.x
- Java 8
- Maven Overlay (The
5.3
branch specifically)
CAS Configuration
First, ensure that your CAS deployment is equipped to act as a SAML2 identity provider. Next, you may also use the JSON Service Registry to keep track of the relying-party registration record in JSON definition files.
The JSON file to contain the service provider relying-party record would be as follows:
{
"@class" : "org.apereo.cas.support.saml.services.SamlRegisteredService",
"serviceId" : "https://www.getrave.com/shibboleth-sp",
"name" : "Rave",
"id" : 1,
"metadataLocation" : "/path/to/metadata.xml",
"encryptAssertions" : false,
"signAssertions" : false,
"signResponses" : true,
"requiredNameIdFormat" : "urn:oasis:names:tc:SAML:2.0:nameid-format:transient",
"attributeReleasePolicy": {
"@class": "org.apereo.cas.services.ReturnMappedAttributeReleasePolicy",
"allowedAttributes": {
"@class": "java.util.TreeMap",
"employeeNumber": "urn:oid:1.2.840.113556.1.2.610",
"eduPersonPrincipalName": "groovy { return attributes['eduPersonPrincipalName'].get(0) + '@example.org' }"
}
}
}
A few things to point out:
- You will need to adjust the
metadataLocation
to match your instance. - Make sure CAS has retrieved the allowed attributes (i.e.
employeeNumber
,eduPersonPrincipalName
etc) listed in the JSON definition file. - Make sure the SP metadata has the correct entity id, matching the Rave instance.
Finale
Thanks to Paul Spaude of Unicon, Inc who was kind enough to share the above integration notes. If you too have an integration with a well-known SAML2 service provider, please consider sharing that guide in form of a blog post here as well.