mirror of
https://github.com/fleetdm/fleet
synced 2026-05-24 09:28:54 +00:00
da01caf3c0
The most common misunderstanding that our users have when configuring SSO (specifically Okta, since it refers to the value by a different name) is what to put in this Entity ID field. If it doesn't match the IdP's version, SSO will fail. We were also directing users to retrieve an issuer URI, which would presumably be used as the Entity ID. The problem is, the rest of our docs don't state that, and instead tell users to use a simple value such as `fleet`. |
||
|---|---|---|
| .. | ||
| add-new-host-modal.png | ||
| distributed-new-query-with-local-filter.png | ||
| distributed-saved-query-with-local-filter.png | ||
| email-two-factor-authentication-576x638@2x.png | ||
| entra-sso-configuration-fleet-config.png | ||
| entra-sso-configuration-step-6.png | ||
| fleet-architecture-diagram.png | ||
| google-sso-configuration-step-1.png | ||
| google-sso-configuration-step-2.png | ||
| google-sso-configuration-step-3.png | ||
| google-sso-configuration-step-4.png | ||
| google-sso-configuration-step-5.png | ||
| google-sso-configuration-step-6.png | ||
| google-sso-configuration-step-7.png | ||
| google-sso-configuration-step-8.png | ||
| manage-queries.png | ||
| my-account-page.png | ||
| my-device-page-turn-on-disk-encryption.png | ||
| my-device-page-turn-on-mdm.png | ||
| nudge-window.png | ||
| okta-idp-setup.png | ||
| sso-setup.png | ||
