Source
Directory, API & administration — found from sitemap — Fleet
Checked for Fleet on 6 Nov 2026
- Page
- https://fleetdm.com/docs/deploy/single-sign-on-sso
- Checked
- 6 Nov 2026, 04:51 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:58b24464eae331b6f4a8b561a18957fbc5ec77221706b1d46c9bb66130d07b32
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
SSO supported idps Report an error
“Fleet supports Okta, authentik, Google Workspace, and Microsoft Active Directory (AD) / Entra ID, as well as any other identity provider (IdP) that supports the SAML standard.”
-
SSO login modes Report an error
“JIT SAML implementation supports just-in-time (JIT) user provisioning, as well as both IdP-initiated login and service-initiated (SP) login.”
-
SSO separate apps Report an error
“If you're configuring SSO for both Fleet users (i.e., IT admins who have access to the Fleet console) and end users (to use with end user authentication), then create two separate apps in your IdP.”
-
SSO callback urls Report an error
“For Fleet users, use https://<your_fleet_url>/api/v1/fleet/sso/callback If you're configuring Require IdP authentication, use https://<your_fleet_url>/api/v1/fleet/mdm/sso/callback”
-
Okta builtin app Report an error
“Okta added a built-in Fleet app and Fleet is testing it internally. Keep in mind that adding push groups will create new fleets. Currently, the best practice is to create a SAML app (instructions below).”
-
No sp metadata Report an error
“Fleet doesn't generate SP metadata XML files. Most major identity providers (like Okta, Microsoft Entra ID, and Google Workspace) work without this file.”
-
SSO configuration path Report an error
“To configure SSO in Fleet head to Settings > Integrations > Authentication (SSO) > Fleet users.”
-
Jit provisioning premium only Report an error
“Applies only to Fleet Premium Fleet can automatically create users using just-in-time (JIT) provisioning.”
-
Jit default role Report an error
“By default, accounts created via JIT provisioning are assigned the global observer role.”
-
Jit role sync on login Report an error
“Fleet will assign role updates everytime a user logs in.”
-
Jit custom roles Report an error
“Users created via JIT provisioning can be assigned Fleet roles using SAML custom attributes that are sent by the IdP in SAMLResponses during login.”
-
Jit role values Report an error
“Currently supported values for the above attributes are: admin, maintainer, observer, observer_plus, technician and null.”
-
Jit role error rule Report an error
“NOTE: Setting both FLEET_JIT_USER_ROLE_GLOBAL and FLEET_JIT_USER_ROLE_FLEET_<FLEET_ID> will cause an error during login as users cannot be both global users and belong to fleets.”
-
Jit name attribute names Report an error
“Your IdP sends the full name of the user as an attribute with any of the following names (if this value is not provided, Fleet will fall back to the user email) name displayname cn urn:oid:2.5.4.3 http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name”
-
SCIM deprovisioning Report an error
“When SCIM is configured with your IdP, Fleet automatically deletes a user's Fleet account when the user is deleted or deactivated in the IdP.”
-
SCIM required attributes Report an error
“Fleet requires the userName, email, givenName, and familyName attributes to be mapped from your IdP for Fleet users.”
-
SCIM reactivation Report an error
“If the user is later reactivated in the IdP, Fleet will automatically recreate the account on the user’s next SSO login, as long as Create user and sync permissions on login in Settings > Integrations > Authentication (SSO) is enabled.”
-
SCIM scope Report an error
“No manual intervention is required. This applies only to SSO-authenticated users. API-only and password-authenticated users are not affected.”
-
SCIM hard delete Report an error
“Fleet deletes the account instead of marking it inactive. Fleet has no deactivated user state, so a deprovisioned user no longer appears in Settings > Users or in the response from the list users endpoint.”
-
SCIM audit log Report an error
“Fleet records each deprovisioning as a deleted_user activity in the audit log. Fleet is the author of this activity, not the admin who configured SCIM.”
-
Authentik idp Report an error
“Fleet can be configured to use authentik as an identity provider. To continue, you will need to have an authentik instance hosted on an HTTPS domain, and an admin account.”
-
Name ID format Report an error
“Name ID Format - The value should be urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress.”
-
End user SSO path Report an error
“If you're configuring end user authentication head to Settings > Integrations > Authentication (SSO) > End users.”
Scores citing this record
- The Mac Fleet Administrator Directory, API & administration
- The Field Operations Lead Directory, API & administration
- The Solo IT Administrator Directory, API & administration
- The MSP Technician Directory, API & administration
- The Information Security Officer Directory, API & administration
- The Skeptic Directory, API & administration