Begin an OIDC identity-linking ceremony
POST/api/v1/auth/identities/oidc/:provider_id/start
Requires a normal authenticated session and a same-origin cookie request. The verified callback can only add a credential to that exact recently authenticated local account; it cannot admit a new account or issue a replacement session.
Request
Responses
- 200
- 401
- 403
- 404
- 421
- 429
- 503
Browser authorization URL and correlation cookie
Response Headers
Always no-store
Host-only HttpOnly OIDC correlation cookie
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The browser mutation did not originate from this application, or the authenticated member lacks the required permission
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
OIDC is disabled
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request authority or direct peer is outside the configured Jiandu ingress boundary
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
OIDC start capacity is busy; retry with backoff
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
A required core dependency is unavailable; retry with bounded backoff
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.