UT Shield

Identity and Access Management

The University of Texas at Austin

Vendor Help

Identity at The University

A great place to start is our Vendor Guide to IAM at UT.

There are a number of ways in which we can assist your engagement with the University:

  • Web-based SSOSSO Single Sign-On (SSO) is a service which allows a user to use one set of credentials to access multiple applications. (Authentication).
  • LDAPLDAP Lightweight Directory Access Protocol (LDAP) is a set of protocols for accessing information directories based on the standards contained within the X.500 standard, but is significantly simpler. Directory Services.
  • Attribute-Based Access Control (ABACABAC Attribute-Based Access Control (ABAC) is a mechanism for managing of user access to information systems based on values of user attributes. Attribute-Based Access Control (ABAC) evaluates the access dynamically, using an algorithm that takes “attributes” as an input, and outputs access decision (allow/deny). The attributes are usually user attributes from the user profile, supplemented with context attributes, such as time of access and user’s current location.) via Group and Role Management.
  • Customized UI for EIDUT EID The University of Texas Electronic Identity (UT EID or EID) is the public records identifier for principals at the university. See our Concepts page for more information. Creation.

Getting Help

If you need help, it’s best to start by reaching out to your University contact. Then, if needed, the sponsoring University department can reach out to our team. This approach provides the following benefits:

  • The sponsoring University department is responsible and accountable for your engagement.
  • Only the sponsoring University department can initiate an engagement with our team.
  • We’ll know which of our 300+ customers you are working with.
  • We won’t mistake your communication for an unsolicited sales contact.

Once contact has been initiated we’ll be happy to join you and your University contact on e-mail threads, conference calls, and the like. While our team primarily uses Microsoft Teams we also support Zoom and, depending on local machine policy, may be able to accommodate other protocols.