![]() Refer to the Release Unified Access Gateway(UAG): RADIUS and RSA SecurID Authentication Failure with Unified Access Gateway (UAG) 21. To get SSO working you'll need to implement TrueSSO. This is a known issue with Unified Access Gateway versions 21.1 and has been resolved in version 2111.2 which is available now. ![]() This in turn gives you all the bells and whistles Azure authentication offers you, but it will require an user to enter their credentials again when logging into the desktop (so no SSO). Option 2 is a direct connection to Azure which users a different Identity Provider compared to VMware Horizon (Active Directory). If everything is configured properly users will fill in their username and password, answer the security prompt on their phones and will successfully be logged in. On the UAG you use the Radius settings to connect to the NPS server. Option 1 requires a NPS server which will be connected to Azure via the NPS Extension. Use all MFA authentication methods (Phone call, text message, app).Use the Microsoft Authenticator App only.In this scenario you have two options for MFA: The SAML Integration also possible with other IDPs like Okta or Azure. Most deployments I do are using separate entries for internal and external user, and the customer wants to use MFA when users are connecting externally. So no more local Password on the UAG Admin UI & you can use Multi Factor Authentication with VMware Verify for example or whatever Authentication rules you set on Workspace ONE Access. It depends on what you want to achieve/what your customer/company wants.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |