QUT ESOE OpenID Connect Provider
QUT's enterprise single sign-on authorization server, a Keycloak deployment on QUT's own address space. Publishes OpenID Connect Discovery 1.0 metadata, an RFC 8414 authorization server metadata document, a JWKS, and endpoints for dynamic client registration, PAR, CIBA, device authorization, introspection and revocation. Discovery is fully public; obtaining a client credential is not, and QUT documents no public route to one.
This API exposes 14 operations across 14 paths, organized into 5 resource areas, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against a single base URL, https://esoe.qut.edu.au/auth/realms/qut.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
QUT ESOE OpenID Connect Provider declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 14 scopes.
By default, every request must be authenticated.
bearerAuth— Access token issued by this realm.oauth2— Scopes below are exactly the scopessupported array of the live discovery document. ServiceAccount, serviceaccount and Integsvctestclient are QUT-specific clien…
Paths & Operations 14
Across 14 paths, the API surfaces 14 operations — 7 GET, 7 POST. They span 5 resource areas: Discovery, Authorization, Token, Identity, Client Registration. Each is listed below with its method, path, parameters, and response codes.
Provider metadata documents.
OAuth 2.0 authorization and device / CIBA initiation.
Token issuance, inspection and revocation.
End-user claims and session termination.
OpenID Connect Dynamic Client Registration.
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are OpenIdProviderMetadata (22 properties), UserInfo (10 properties), TokenRequest (10 properties), TokenResponse (8 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
This is an independent, third-party profile of QUT ESOE OpenID Connect Provider, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.