Ucsi Authentication
What can actually be established about how a client authenticates against anything UCSI University operates. UCSI publishes no public API and no developer documentation, so this artifact describes the one authentication surface that is publicly readable: the OpenID Connect / SAML 2.0 metadata of the institution's own Microsoft Entra ID tenant. It is a record of a probed discovery document, not a description of an API programme UCSI does not run. Access to a UCSI application still requires a UCSI-issued account and an application registration inside the tenant; there is no self-serve onboarding.
UCSI University secures its APIs with oauth2, openIdConnect, and saml2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode, implicit, and deviceCode flow(s).
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.