Chula SSO Authentication API
The university's own single sign-on service, in production at account.it.chula.ac.th since January 2017 and originally built as part of the 2015 CU DataGateway project. The protocol is a modified CAS 1.0 flow with an application-authentication step layered on top: a relying application presents a DeeAppId / DeeAppSecret pair alongside the user's ticket, so the SSO controls which applications may authenticate a Chula ID, and users never hand credentials to the relying application. The public wiki documents /login, /logout and /serviceValidation with their parameters, headers and JSON response bodies — unusually complete prose for this cohort. What it does not do is publish a machine-readable contract or offer self-service registration: keys are requested by email from the architect named on the wiki. The OpenAPI recorded here is an API Evangelist transcription of that page, marked derived, not something the university published.
Chula SSO Authentication API is one of 10 APIs that Chulalongkorn 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, Single Sign-On, Authentication, CAS, and Education. The published artifact set on APIs.io includes API documentation, an API reference, an OpenAPI specification, authentication docs, and 1 JSON Schema.
This API exposes 4 operations across 3 paths, organized into 2 resource areas, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 2017.01.
Requests are made against a single base URL, https://account.it.chula.ac.th.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Chula SSO Authentication API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as DeeAppId (DeeAppId).
An API key is passed in the header as DeeAppSecret (DeeAppSecret).
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 3 GET, 1 POST. They span 2 resource areas: Authentication, Validation. Each is listed below with its method, path, parameters, and response codes.
Session establishment and teardown
Ticket validation for relying applications
Schemas 2
The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are SSOUser (6 properties), SSOError (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Chulalongkorn University 9
Other APIs Chulalongkorn University publishes across the network.
This is an independent, third-party profile of Chula SSO Authentication API, 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.