Does Keka support SSO within an Android Enterprise Work Profile?

Keka supports Single Sign-On using configured identity providers such as Microsoft Entra ID, Google Workspace, Okta, OneLogin, and JumpCloud. Internal documentation also confirms that Keka supports OAuth 2.0 and OpenID Connect authentication for SSO, including authentication on mobile devices. 

However, Keka does not currently have documented or officially verified support specifically for SSO authentication within an Android Enterprise Work Profile.

Authentication in a Work Profile can depend on several external configurations, including:

• The organization’s Enterprise Mobility Management provider
• Work Profile restrictions and managed app policies
• The configured identity provider
• The availability and configuration of the identity provider’s authentication or broker application inside the Work Profile

Therefore, successful SSO authentication in this environment cannot be guaranteed based only on Keka’s standard SSO support.

Recommended next steps

If your organization uses Keka within an Android Enterprise Work Profile:

1. Confirm that Keka and the required identity provider application are deployed inside the Work Profile.
2. Review authentication and app protection policies configured in your EMM solution.
3. Test the login flow with a limited group of managed devices.
4. Contact Keka Support with the device model, Android version, EMM provider, identity provider, and relevant error details if authentication fails.

Note: General mobile SSO availability should not be treated as confirmation of compatibility with every Android Enterprise or EMM configuration.