Qatar University Single Sign-On (OpenID Connect / OAuth 2.0)
Qatar University's own OpenID Connect provider, running on a WSO2 Identity Server at sso.qu.edu.qa. It publishes a complete OpenID Connect Discovery 1.0 document, a live JWKS serving an RS256 signing key, and authorization, token, userinfo, introspection, revocation, logout, session-check and dynamic-client-registration endpoints. Five scopes are supported — the five OIDC standards, with nothing institution-specific — and thirty claims, including the non-standard `groups` and `upn`. Client registration is institutional; there is no public self-service onboarding. This is the most complete machine-readable contract in the profile and it was entirely absent from the June 2026 pass. It is also, as published, unreadable to a conformant client: the host serves an incomplete TLS chain, the issuer names the WSO2 management port, and the discovery document sits at a non-RFC-8414 location.
Qatar University Single Sign-On (OpenID Connect / OAuth 2.0) is one of 10 APIs that Qatar University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Identity Federation, OpenID Connect, OAuth 2.0, Single Sign-On, and Authentication. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and 1 JSON Schema.
This API exposes 10 operations across 10 paths, organized into 4 resource areas, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.
Requests are made against a single base URL, https://sso.qu.edu.qa.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Qatar University Single Sign-On (OpenID Connect / OAuth 2.0) declares
3 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerToken).
It accepts HTTP basic authentication (clientSecretBasic).
An API key is passed in the header as Authorization (clientSecretPost).
bearerToken— Access token issued by this provider, presented on the UserInfo endpoint.clientSecretBasic— OAuth 2.0 client credentials in the Authorization header (clientsecretbasic).clientSecretPost— clientsecretpost — clientid and clientsecret carried in the form body. Modelled here as a named scheme because OpenAPI has no first-class representation for it.
Paths & Operations 10
Across 10 paths, the API surfaces 10 operations — 6 GET, 4 POST. They span 4 resource areas: Discovery, OpenID Connect, OAuth, Client Registration. Each is listed below with its method, path, parameters, and response codes.
Provider metadata and signing keys.
Authorization, user info and session management.
Token issuance, introspection and revocation.
OpenID Connect Dynamic Client Registration.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are OpenIdConfiguration (17 properties), TokenResponse (6 properties), OAuthError (2 properties), Jwks (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Qatar University 9
Other APIs Qatar University publishes across the network.
This is an independent, third-party profile of Qatar University Single Sign-On (OpenID Connect / OAuth 2.0), 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.