Tag: Workspace ONE

  • Notes from the field: Configuring Autotask PSA with VMware Workspace ONE Access

    Autotask PSA SSO configuration can be found at the following url: https://ww13.autotask.net/help/Content/AdminSetup/1FeaturesSettings/ResourcesUsers/Security/SSSO_OIDC.htm For the configuration part of Workspace ONE Access SSO you can see the available API at this url: https://code.vmware.com/apis/57/idm#/ The problem is that Autotask PSA SSO doesn’t work/supports the setup of VMware Workspace ONE Access. I worked around this issue by having a…

  • Notes from the field: Configuring OpsGenie (without Atlassian Access) with VMware Workspace ONE Access

    OpsGenie can use SAML SSO without the use of Atlassian Access, see the following url: https://docs.opsgenie.com/docs/single-sign-on-with-opsgenie For the configuration part of Workspace ONE Access just add a new manual SAML 2.0 application and provide the following information according to above article: Single Sign On URL https://app.opsgenie.com/auth/saml?id=”uniquesamlidprovided Recipient URL https://app.opsgenie.com/auth/saml?id=”uniquesamlidprovided Application ID https://app.opsgenie.com/auth/saml?id=”uniqesamlidprovided Username Format =…

  • Notes from the field: Configuring Atlassian Access with Workspace ONE Access

    Atlassian Access is the SSO portal being used for SSO access across Jira, Confluence etc. for the configuration part see the following url: https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html For the configuration part of Workspace ONE Access just add a new manual SAML 2.0 application and provide the following information according to above article: Single Sign On URL https://auth.atlassian.com/login/callback?connection=saml”uniquesamlidprovided Recipient…

  • Notes from the field: UEM/vIDM integration caveats

    Not too long ago I encountered some issues when configuring UEM and IDM integration. When providing the vIDM URL in UEM for configuring the integration it would error out with below error: After some troubleshooting it appeared that the access policies where not properly configured as in the last rule in the default access application…

  • Notes from the field: vIDM and o365 modern authentication delay

    Just a quick win blog to mention and give a heads-up that when you are in the process of configuring vIDM and o365 you might encounter native clients prompting for authentication and a big ass delay when you flip over the authentication and the requested domain from managed to federated with vIDM. This might be…