sso_required
HTTP status: 403 Forbidden
The organization requires single sign-on, and the token on this request wasn’t created through its identity provider. The response carries a connection_id naming the SSO connection to sign in with.
This is separate from forbidden, which means the token’s role can’t perform the action.
Common causes
Section titled “Common causes”- The personal access token was created during a password, Google or GitHub session, and an Owner has since turned on Require single sign-on.
- The token belongs to a different organization’s SSO session.
- The token was created during an SSO session, and an Owner has since deactivated the connection or changed its issuer or client ID.
How to fix
Section titled “How to fix”- Sign in to Featureflip with Continue with SSO, create a new personal access token, and use that one.
- Retire the old token once the new one works.
Example
Section titled “Example”{ "error": "sso_required", "message": "This organization requires single sign-on.", "connection_id": "3f2b8c1e-5d4a-4e7b-9a61-0c2d8e4f7a95", "docs_url": "https://featureflip.io/docs/management-api/errors/sso_required"}