The basic information you’ll need to integrate one of our authenticationAuthentication Authentication is the act of determining that a person is who they claim to be. For more information, see our Concepts page. services can be found below:
Enterprise Authentication
In order for you application to work with Enterprise Authentication, it must support one of the following industry standard authentication protocols:
- Security Assertion Markup Language (SAMLSAML Security Assertion Markup Language (SAML) is a standard, XML-based language for exchanging authentication and authorization data between identity providers and service providers. This standard is currently used by Enterprise Authentication (as well as hundreds of service providers that integrate with our identity provider).) 2.0
- OpenID Connect (OIDCOIDC OpenID Connect 1.0 (OIDC) is an authentication layer built on OAuth 2.0 where the identity provider that runs the authorization server also holds the protected resource that the third-party application aims to access.) 1.0
Enterprise Authentication does not support OAuth 2.0 for authentication. OAuth is an authorizationAuthorization Authorization refers to the act of determining whether an authenticated user is allowed to access a specific resource or take a specific action. For more information, see our Concepts page. protocol, not an authentication protocol.
| Data | Value |
|---|---|
| Entity ID | https://enterprise.login.utexas.edu/idp/shibboleth |
| IdPIdP An Identity Provider (IdP) is a software tool or service that offers user authentication as a service. The IdP manages the user's primary authentication credentials and issues assertions derived from those credentials. At UT Austin, the primary IdP used to authenticate the UT EID and EID Password is Enterprise Authentication, which is managed by the IAM Team. For more information, see our Concepts page. Metadata URLURL A Uniform Resource Locator (URL) is a reference to a web resource that specifies its location on a computer network and a mechanism for retrieving it. A typical URL could have the form http://www.example.com/index.html, which indicates a protocol (http), a host name (www.example.com), and a file name (index.html). Also sometimes referred to as a web address. | https://enterprise.login.utexas.edu/idp/shibboleth |
| Logout Endpoint | https://enterprise.login.utexas.edu/idp/profile/Logout |
| Preferred Name ID Format | urn:oasis:names:tc:SAML:2.0:nameid-format:transient |
Guest Authentication
| Data | Value |
|---|---|
| Entity ID | https://guest.login.utexas.edu/idp |
| IdP Metadata URL | https://guest.login.utexas.edu/simplesaml/module.php/saml/idp/metadata |
| Logout | https://guest.login.utexas.edu/simplesaml/module.php/saml/idp/singleLogout |
| Preferred Name ID Format | urn:oasis:names:tc:SAML:2.0:nameid-format:transient |
Specifications
| Standard | Specifications |
|---|---|
| SAML v2.0 Standard | https://wiki.oasis-open.org/security/FrontPage |
| OIDC v1.0 Standard | https://openid.net/developers/specs/ |
Go back to the Vendor Guide to IAM at UT.
