About this role
How Addigy Identity works
Simpler login. IdP credentials at the Mac login; passwords stay synced both ways; branded screens per policy; offline login with last-known password; FileVault compatible; optional emergency bypass; MFA enforced through IdP; admin-vs-standard privileges; pilot mode to test flows.
What customers say about Addigy Identity
We’re reducing moving parts and saving time. Automating management cuts the time to assign devices from minutes to seconds; full device setup that used to take 15 minutes now takes 3–5 minutes because things are automated.
Frequently Asked Questions
Which IdPs for SSO enrollment? Microsoft Entra ID (Azure AD), Okta, Google Workspace, and OneLogin; works with Apple Automated Device Enrollment across macOS, iOS, iPadOS, tvOS. For the macOS login window, Addigy Identity supports Microsoft Entra ID, Okta, and Google Workspace.
How to configure Addigy with Azure AD, Okta, or Google? Create the SAML/OIDC app in the IdP, paste Entity ID and ACS URL from Addigy into the IdP, then assign users. For enrollment, map Entity ID, ACS URL, and SAML certificate to a new enterprise app. Only users assigned to the app can enroll or log in.
Does Addigy Identity support macOS login window SSO? Yes—via two options: replacing the native login with an IdP-backed login, or Extensible SSO with Platform SSO. The two can coexist to provide just-in-time provisioning and ongoing Platform SSO.
Does Addigy Identity work offline or when the IdP is unreachable? Yes. It supports offline logins with the last known password and is compatible with FileVault; an emergency bypass is available for admins.
Setup time? Under 30 minutes in most environments; configured from Account > Integrations; pilot mode available for testing.
Does Addigy Identity sync passwords and user attributes from the IdP? Yes. Passwords stay in sync and attributes like department, location, and title can drive policy, privileges, and asset tracking.