Unicon recently completed a project for the Colorado School of Mines to setup a continuous integration/continuous delivery (CI/CD) pipeline that can be used as a template for their work modernizing their application deployment processes going forward.
You have paid your InCommon membership dues, your federation admins have been vetted, and you even uploaded your IdP metadata in the InCommon Federation Manager website. Like many new members, you are probably asking yourself, "Now what?"
Many Shibboleth IdP adopters use LDAP as provide both an authentication provider and an attribute source. There is always the question of "do we need to configure TLS/SSL for the IdP's connection to the LDAP server(s)?". My response is "always" because we need to protect the user's credentials even in the most trusted network. My question back to the client, "Why do wouldn't you?". Often the response is somewhere between "we've tried and we got it to work once, but then it broke sometime" and "we could never get it to work".
A common task when running a SAML Identity Provider (IdP) is integrating additional SAML service providers (SP). This task is not a trivial one, especially when compared to integrating CAS clients. New IdP administrators can run into problems before they even start with the technical task at hand because they aren't given the correct information to be successful. The request to do an integration usually goes something like this:
On November 5th, we had a great quarterly IAM briefing. Misagh Moayyed, Jonathan (JJ) Johnson, and David Langenberg presented to me to discuss CAS, Shibboleth, and Grouper. This webinar was recorded.
On July 9th, we had a great IAM briefing. Misagh Moayyed, Jonathan (JJ) Johnson, and David Langenberg presented to us. This webinar was recorded. You can watch the recording, or just checkout the slides.
Here are some highlights:
The shib-cas-authn extensions, developed as part of Unicon's Open Source Support program, is used to delegate the Shibboleth IdP's user authentication to a CAS Server. Whether the client application is a CAS client or a Shibboleth/SAML SP, the integration presents the user with a single SSO experience. Today, Unicon's IAM team released the next version of the shib-cas-authn extension.
Note: This webinar was recorded. Watch the recording.
During this briefing we will discuss:
A client was testing our integration between CAS Server 3.5.2.1 and Moodle 2.6. The lead tester reported that it was often requiring two authentications attempts to login into CAS Server after being redirected there from Moodle. Interestingly enough I was rarely able to invoke the same symptom. The exact symptom is that a user sees the login page, enters their credentials, and after hitting the Login button, the user is show an empty login form. There is no error message, no pre-populated username field. Just the empty login form.
John Gasper has worked in IT for 18 years. He's worked in the SSO & IAM space for 5-6 years.
Except where otherwise noted in our copyright notice, content on this site is
licensed under a Creative Commons Attribution-Noncommercial-ShareAlike 3.0 United States License.
Privacy Policy
