开发者文档目前仅提供英文版。
AD FS 2019+
Connecting Active Directory Federation Services to a Calab workspace over OpenID Connect with PKCE S256.
AD FS connects over OpenID Connect. Only AD FS 2019 and newer is supported: older versions lack PKCE S256, and Calab refuses sign-in without it. General requirements are on the OpenID Connect page.
Know this first
| Requirement | How to check |
|---|---|
| AD FS 2019+ | https://adfs.example.com/adfs/.well-known/openid-configuration contains "code_challenge_methods_supported" with "S256". If the list is missing or lacks S256, the connection test and sign-in fail |
| Public address or operator approval | AD FS on an internal network is reachable by Calab only if the operator allowed its URL (see for operators) |
auth_time in the ID token | Mandatory, as for every provider |
| Client authentication | client_secret_post — Calab picks it for AD FS automatically |
The AD FS issuer is usually https://adfs.example.com/adfs — check the issuer field in discovery and copy it exactly.
Step 1. An application group in AD FS
In the “AD FS Management” console:
- “Application Groups” → “Add Application Group”.
- The “Server application” template (a confidential client with a secret). Name — for example,
Calab. - Note the Client Identifier.
- Redirect URI —
https://id.example.com/api/auth/sso/callback/<connection-id>. The connection ID appears after step 2; you can add the URI later in the application's properties. - “Generate a shared secret” — copy it, it's shown once.
- Make sure the application is permitted the
openidscope.
Step 2. The connection in Calab
Workspace settings → “SSO settings” → “SSO connection”:
| Field | Value |
|---|---|
| “Name” | For example, “Sign in with AD FS” |
| “Provider” | “AD FS 2019+” |
| “Issuer URL” | The issuer value from discovery, e.g. https://adfs.example.com/adfs |
| “Client ID” | The Client Identifier |
| “Client secret” | The shared secret |
Click “Save”. Take connection.id from GET /api/workspaces/{workspace_id}/identity and add the redirect URI in AD FS.
Step 3. Link, test, activate
- “Link corporate identity” — link your own account.
- “Test and activate” → “Test sign-in in browser”.
- Within 5 minutes — “Activate tested connection”.
Directory
AD FS handles sign-in only. For Calab to learn about disabled accounts and group removals, connect the directory — the same Active Directory over LDAPS.
Common errors
| Symptom | Cause |
|---|---|
| The test fails at once | Discovery lacks S256 (AD FS older than 2019) or issuer doesn't match what you entered |
| AD FS shows a redirect URI error | The redirect URI in AD FS doesn't match the connection's address |
| “identity access denied” after sign-in | No auth_time in the ID token, a wrong secret, or the sign-in used a different account than the linked one |
More in troubleshooting.