- Performed regression testing of the most recent tag (3.4.6_20191001) of the InCommon Trusted Access Platform (TAP) Shibboleth Identity Provider (IdP) image.
- Updated Enterprise Authentication to use tested tag.
- No user-facing changes.
Enterprise Authentication Changelog
Enterprise Authentication is LIVE
The implementation of the new Enterprise Authentication service is complete, and the service is now live in production.
The Identity and Access Management (IAM) team is now undertaking the first phase of a project to migrate over 800 integrations from UTLogin to Enterprise Authentication. Transition managers are working to schedule customer transitions with the goal to have all UTLogin transitions complete by the end of 2020 and retire UTLogin in December 2020. The transition focus will then shift to transitioning UT Shibboleth customers.
Ready to Integrate with Enterprise Authentication?
If you are an existing UTLogin customer and have not been contacted by a transition manager, please reach out to the team by emailing firstname.lastname@example.org .
New IAM authentication customers can find information about the integration process and initiate a new integration by visiting https://iamservices.utexas.edu/integration/.
All customers are welcome to visit the Enterprise Authentication ServiceNow page to find more information including answers to frequently asked questions.
Want to know more about Enterprise Authentication? Visit the Enterprise Authentication ServiceNow page and/or review some of these commonly asked-about topics:
- KB0017765: UTLogin to Enterprise Authentication Transition Plan
- KB0017642: Transitioning from a UTLogin WPA to Enterprise Authentication
- KB0017671: Metadata Requirements
- KB0017644: Mapping Policy Agent Headers to Enterprise Authentication Attributes
- KB0017849: Shibboleth Service Provider (SP) Metadata Examples
- KB0017850: SimpleSAMLphp Examples
You may also be interested in our other ServiceNow Knowledge Articles.
Connect with the Enterprise Authentication Team
For questions or comments, send an email to email@example.com.
What is changing and why?
The Identity and Access Management (IAM) team is deprecating the agent-based authentication model and adopting standards-based web authentication.
For UT servers and applications using UTLogin, this will involve transitioning to a new Enterprise Authentication service, which provides Security Assertion Markup Language (SAML 2).
The goal of this change is to provide a standards-based authentication method. SAML 2 represents established industry standards, which the majority of software vendors support. Additionally, having fewer authentication methods means a better single sign-on experience and faster integrations.
The IAM team will begin contacting UTLogin customers to develop transition plans in June 2019.
How will this affect me?
For most people who use protected websites and applications, the transition to Enterprise Authentication will not require any attention or action. There may be small changes to the look and feel of the login screens; but, overall, the login process will be the same. Some end users may be asked to authenticate multiple times as our authentication customers migrate to the new service.
This change primarily impacts individuals who manage servers and web applications that use UTLogin. In order to focus on the transition to Enterprise Authentication, the IAM Team will no longer provision new Web Policy Agents (WPAs). Support for existing WPA and SAML customers will not be affected.
The IAM team has been working to develop processes to support transitioning customers to Enterprise Authentication. This includes documentation, training, and outreach. These efforts will continue and become more detailed over the coming months.
Review our project page: Transition to Enterprise Authentication Project
Please send questions to: firstname.lastname@example.org