Nanjing University Unified Identity Authentication (CAS SSO)

NJU's central single sign-on, a CAS deployment supporting password, verification-code, biometric and QR-code login. It is not a developer API and there is no public service registration — a relying application must be registered by NJU IT — but the ticket validation endpoints do speak the CAS protocol to anonymous callers and return application/xml, which makes this a real machine-readable institution-operated surface rather than the login page the June 2026 profile recorded.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/cas-sso"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: nanjing:cas-sso
name: Nanjing University Unified Identity Authentication (CAS SSO)
description: NJU's central single sign-on, a CAS deployment supporting password, verification-code, biometric
  and QR-code login. It is not a developer API and there is no public service registration — a relying
  application must be registered by NJU IT — but the ticket validation endpoints do speak the CAS protocol
  to anonymous callers and return application/xml, which makes this a real machine-readable institution-operated
  surface rather than the login page the June 2026 profile recorded.
humanURL: https://itsc.nju.edu.cn/itsc_en/68/6a/c26812a485482/page.htm
baseURL: https://authserver.nju.edu.cn/authserver/
x-operator: institution
x-operator-evidence: 'authserver.nju.edu.cn resolves to 219.219.115.212, APNIC netname CERNET-CN. Probed
  2026-09-01: /authserver/login 200; /authserver/serviceValidate and /authserver/p3/serviceValidate both
  200 application/xml returning <cas:serviceResponse> with <cas:authenticationFailure code="INVALID_TICKET">;
  /authserver/.well-known/openid-configuration 404 (JSON) — no OIDC surface is published.'
tags:
- Authentication
- SSO
- CAS
- Identity
properties:
- type: Documentation
  url: https://itsc.nju.edu.cn/itsc_en/68/6a/c26812a485482/page.htm
- type: Authentication
  url: https://authserver.nju.edu.cn/authserver/login