No, if you are using an API key (authentication token) generated by Clarizen, and even if Clarizen is configured with ADFS, the API token authentication will not go through ADFS or Active Directory.
✅ Here’s why:
- Clarizen API tokens are tied to local Clarizen users, not to SSO accounts.
- These tokens are validated internally by Clarizen, not by your ADFS or AD infrastructure.
- Even in SSO-enabled environments, API tokens bypass ADFS because:
- ADFS is only used during interactive user login (SSO via browser).
- API token auth is handled entirely within Clarizen, without federated identity checks.
🔒 So in short:
🧠Important Note:
- If your Clarizen users are forced to log in via ADFS, you cannot use API tokens with those accounts unless a local password (non-SSO) user account exists in Clarizen.
- Therefore, for API integration, organizations typically:
- Create a dedicated local user in Clarizen (e.g., api.integration@yourdomain.com),
- Generate an API token for that user,
- Use that token in integrations (e.g., in middleware, custom scripts, or automation tools).