Apereo CAS - VMware Identity Manager SAML2 Integration


Collaborate
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.
Contributed Content
Keith Conger of Colorado College, an active member of the CAS community, was kind enough to contribute this guide.

VMware Identity Manager is identity management for the mobile cloud era that delivers on consumer-simple expectations like one-touch access to nearly any app, from any device, optimized with AirWatch Conditional Access. As a SAML2 service provider, VMware Identity Manager 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:

VMware Identity Manager Configuration

  • Register CAS as an identity provider

  • Configure authentication methods

screen shot 2018-11-27 at 3 01 55 pm

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 VMware Identity Manager relying-party registration record in JSON definition files.

The JSON file to contain the VMware Identity Manager registration record would be as follows:

{
  @class: org.apereo.cas.support.saml.services.SamlRegisteredService
  serviceId: your-vmware-idm-entity-id
  name: VMware Identity Manager
  id: 1
  description: VMware Identity Manager
  attributeReleasePolicy:
  {
    @class: org.apereo.cas.services.ReturnMappedAttributeReleasePolicy
    allowedAttributes:
    [
      @class: java.util.TreeMap
      givenName: [ java.util.ArrayList [ firstName ] ]
      mail: [ java.util.ArrayList [ email ] ]
      sAMAccountName: [ java.util.ArrayList [ userName ] ]
      sn: [ java.util.ArrayList [ lastName ] ]
      userPrincipalName: [ java.util.ArrayList [ userPrincipalName ] ]
    ]
  }
  metadataLocation: /path/to/vmware-idm.xml
  signAssertions: true
  skipGeneratingSubjectConfirmationNotBefore: true
  signResponses: true
}

A few things to point out:

  • You will of course need to adjust the serviceId and metadataLocation to match your data and VMware Identity Manager instance.
  • Make sure CAS has retrieved the allowed attributes (i.e. mail, givenName, etc) listed in the JSON definition file.

Finale

Thanks to Keith Conger of Colorado College 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.

Misagh Moayyed

Related Posts

CAS 6.1.0 RC4 Feature Release

...in which I present an overview of CAS 6.1.0 RC4 release.

Apereo CAS - Multifactor Provider Selection

Learn how to configure CAS to integrate with and use multiple multifactor providers at the same time. This post also reveals a few super secret and yet open-source strategies one may use to select appropriate providers for authentication attempts, whether automatically or based on a menu.

Apereo CAS - Dockerized Hazelcast Deployments

Learn how to run CAS backed by a Hazelcast cluster in Docker containers and take advantage of the Hazelcast management center to monitor and observer cluster members.

Apereo CAS - Configuration Security w/ Jasypt

Learn how to secure CAS configuration settings and properties with Jasypt.

CAS 6.1.0 RC3 Feature Release

...in which I present an overview of CAS 6.1.0 RC3 release.

Apereo CAS - Webflow Decorations

Learn how you may decorate the Apereo CAS login webflow to inject data pieces and objects into the processing engine for display purposes, peace on earth and prosperity of all mankind, etc. Mainly, etc.

Apereo CAS - SAML2 Metadata Query Protocol

Learn how you may configure Apereo CAS to fetch and validate SAML2 metadata for service providers from InCommon's MDQ server using the metadata query protocol.

Saving Time is Time Consuming

May you live in the best of times. May you live in the startup times.

Apereo CAS 6.1.x - Credential Caching & Proxy AuthN

Learn how you may configure Apereo CAS to capture and cache the credential's password and the proxy-granting ticket in proxy authentication scenarios, pass them along to applications as regular attributes/claims. We will also be reviewing a handful of attribute release strategies that specifically affect authentication attributes, conveying metadata about the authentication event itself.

Apereo CAS 6.1.x - Attribute Repositories w/ Person Directory

An overview of CAS attribute repositories and strategies on how to fetch attributes from a variety of sources in addition to the authentication source, merge and combine attributes from said sources to ultimately release them to applications with a fair bit of caching.