Comments

  • A more scalable way than "per product/per user configuration" would be to use a mobile device management (MDM) solution to register, deploy apps, apply policy and conditions to a user's phone. Here is an example: https://learn.microsoft.com/en-us/mem/intune/fundamentals/deployment-guide-platform-android or look up JAMF,…
  • On 5/3/24 Microsoft announced the public preview of External Authentication Methods - Preview which will enable providers of MFA (WatchGuard) and MSPs (You) to add a MFA provider to your customers EntraID tenant. The preview is open now and we will announce our beta later this year. Learn more before the beta…
  • Windows Hello and UAC is supported in the v3.2 version of the Agent for Windows for admins and protected users to go passwordless and verify privilege elevation (vs. consent). It can also be installed on Windows Server. Kerberos is supported in Windows and Windows Server. To support Kerberos SSO, your network requires: A…
  • Thank you very much Chris, we have an all new User Experience Design refresh in 2024, we hope you love it.
  • OIDC coming in 2024!
  • Does Verkada support SSO? It needs to be SAML 2.0 capable--if it is, then you can add it to the Application Portal and configure it just like any SaaS/Webapp. It doesn't require any integration from AuthPoint, you would need a guide to follow--which they should provide.
  • FIDO 2.0 is a credential type, not a token and they are device bound. We do not have a strategy to BYO HW Tokens / Passkey credentials issued by third-parties to our platform.