This article applies to:
- Onboarding
- Product edition: All versions
- Feature Category: Integration.
Problem Description : VMware Workspace ONE Access delivers multifactor authentication (MFA), conditional access and single sign-on (SSO). By acting as a broker to other identity stores and providers, Workspace ONE Access enables organizations to deliver secure and consistent enterprise-wide access to applications and data. After you’ve completed the VMware Aria Operations for Applications integration for Workspace ONE Access setup, all users in your enterprise that can authenticate to Workspace ONE Access can also log in to your VMware Aria Operations for Applications instance. All instructions are mentioned over the wavefront doc page, how to set this setup in customer environment but there is confusion with Application ID/Entity ID mentioned in setup instruction.
Cause: While configuring the setup, we have to provide application ID on step 5. Which
should be unique identifier for application. But sometimes it makes confusion as : Is there an unique URL we need to set for this? Or is this not required for the SAML assertion, and it can be set to anything?
Resolution: Customer can mention unique identifier for application or can mention VMware Aria Operations for Applications URL. It will help further to set this setup in customer environment.
Exam:
For more information on these settings, please refer to the article: https://docs.wavefront.com/workspace-one.html#vmware-workspace-one-access-setup
Comments