Keio Okta Tenant — OpenID Connect

Keio runs an Okta tenant at keio.okta.com behind its campus applications; gslbs.keio.jp redirects an anonymous request into a SAML authentication request against it. The tenant's OpenID Connect discovery document is anonymously readable and advertises authorization, token, userinfo, JWKS and client-registration endpoints. The tenant, the users and the applications are Keio's; the identity service, its contract and its engineering are Okta's, and the discovery document is the one Okta publishes for every org — so Okta's contract is deliberately not saved under this institution. Readable, but not consumable: a client_id exists only if Keio IT creates one.

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/okta"
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: keio:okta
name: Keio Okta Tenant — OpenID Connect
description: 'Keio runs an Okta tenant at keio.okta.com behind its campus applications; gslbs.keio.jp
  redirects an anonymous request into a SAML authentication request against it. The tenant''s OpenID Connect
  discovery document is anonymously readable and advertises authorization, token, userinfo, JWKS and client-registration
  endpoints. The tenant, the users and the applications are Keio''s; the identity service, its contract
  and its engineering are Okta''s, and the discovery document is the one Okta publishes for every org
  — so Okta''s contract is deliberately not saved under this institution. Readable, but not consumable:
  a client_id exists only if Keio IT creates one.'
humanURL: https://keio.okta.com/
baseURL: https://keio.okta.com/.well-known/openid-configuration
tags:
- Single Sign-On
- OpenID Connect
- OAuth
- Identity
- Gated
properties:
- type: Authentication
  url: authentication/keio-authentication.yml
- type: Examples
  url: examples/keio-okta-openid-configuration.json
x-operator: tenant
x-operator-evidence: keio.okta.com is a Keio-specific tenant subdomain on Okta's shared identity platform.
  The issuer, endpoints and document shape are Okta's standard org configuration, identical for every
  customer.
x-operator-note: 'audit-university-contracts.py returns `federation` for this host, because its rule reads
  any identity host as a federation carrying the institution''s own IdP. `tenant` is kept deliberately
  as the more precise verdict: an Okta org is a commercial platform tenancy, not a national or interfederation
  registry, and Keio''s actual federated identity lives in the separate keio:gakunin-idp entry. Both verdicts
  agree the relationship is real and must never be deleted; only the label differs.'
x-access: gated
x-status: 200 on both the org and default authorization-server discovery documents (probed 2026-09-01)