Integration
Understand Concepts
When considering development or acquisition of a new application, it's important to understand some core identity concepts.
Prior to submitting a request, please review the following:
To improve security and streamline access management, we are deprecating legacy single sign-on (SSO) protocols CAS and Shibboleth and will only allow SAML or OpenID Connect (OIDC) via Microsoft Entra ID going forward. SAML and OIDC are modern, standards-based protocols that provide enhanced authentication, authorization, and federation capabilities compared to older protocols like CAS and Shibboleth. By consolidating on SAML and OIDC via Microsoft Entra ID, we will be able to leverage improved security features, reduce complexity, and gain greater visibility into access and usage through unified logging and reporting. Exceptions will be made on a case-by-case basis where there is a compelling business need to maintain legacy protocol support, but the long-term goal is to fully transition to SAML and OIDC via Entra ID for all SSO integration. This change will improve our security posture while also streamlining access management as part of our continued efforts to mature our identity and access management practices.
Review Requirements
Prior to purchasing a vendor solution, please review our Vendor Requirements to ensure that your solution will work with our Identity Provider (IdP).
Submit Request
Please note that the typical time to onboard a new integration is a minimum of 1 week if we will be working with an external vendor.
Related Approvals
If you plan to use cloud computing services, the services may need to be compliant with the Texas Risk and Authorization Management Program (TX-RAMP).
Configure, Test, and Verify
We will assign your request to one of our team members who will work with you to configure, test, and verify your integration.