StevenDSa Tracker

Re: Steve's IDM Blog been removed?

StevenDSa — Tue, 15 Jun 2021 13:57:52 GMT

It was an unintentional casualty of the platform upgrade. It worked out better for me in the long run as my new blog give me a better layout with menus, categories and search functions.

Re: Steve's IDM Blog been removed?

StevenDSa — Wed, 11 Nov 2020 15:02:31 GMT

You can now find my blog at https://stevetheidentityguy.wordpress.com/blog/

How to Debug IOS Mobile Traffic

StevenDSa — Fri, 14 May 2021 15:02:50 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Using Workspace ONE Access as a Claims Provider in ADFS

StevenDSa — Fri, 14 May 2021 15:05:33 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Integrating DUO with Workspace ONE Access

StevenDSa — Fri, 14 May 2021 15:00:53 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Re: Workspace ONE - Okta Integration Part 4: Device Trust

StevenDSa — Wed, 30 Sep 2020 16:52:52 GMT

Workspace ONE UEM will deploy a certificate payload to the managed Win10 device. Workspace ONE Access will issue a certificate challenge to the device based on the root certificate uploaded in WS1 Access. Using the Device ID which is part of the SAN attributes on the certificate, WS1 Access will make an API call to UEM to retrieve the device compliance status.

Using SCIM with OneLogin and Workspace ONE Access

StevenDSa — Tue, 15 Jun 2021 14:37:25 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Integrating Zoom with Workspace ONE Access

StevenDSa — Tue, 15 Jun 2021 14:36:58 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Extending the Workspace ONE Application in Okta for Additional Attributes

StevenDSa — Tue, 15 Jun 2021 14:36:29 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Using the AirWatch Provisioning Adapter with Windows 10 AAD Join

StevenDSa — Tue, 15 Jun 2021 14:36:02 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Re: Workspace ONE - AirWatch Provisioning App

StevenDSa — Wed, 24 Jun 2020 20:13:50 GMT

I've not seen that one before. Here are some suggestions:

Make sure there is no directory configured at the customer level OG in UEM
Make sure customer level OG is specified in WS1 Access.
Assuming the same group does not already exist in UEM?
Make sure Chrome autofill did not change the username/password for Provisioning tab
Wait for it to fail (might take some time). Hopefully the error can point us in the right direction or give us the ability to deprovision.

Re: Workspace ONE - AirWatch Provisioning App

StevenDSa — Tue, 23 Jun 2020 20:04:43 GMT

Can you change your UEM settings from Redirect to Post?

Re: Workspace ONE - AirWatch Provisioning App

StevenDSa — Thu, 18 Jun 2020 21:55:50 GMT

I don't know if I'll have the right answers for you but based on your comment "From the web using cnXXXX.awmdm.com we are not redirected to Okta and get "Invalid credentials, Try again."

If you go to in your browser: https://cnXXXX.awmdm.com/mydevice/Login?gid=OG

You should be redirected to WS1 Access and then Redirected to Okta. If this is not happening then you most likely have an issue in Enterprise Integration -> Directory Services (Specifically Under SAML Settings)

If you are having a problem on the return, its probably an issue with the values being passed in the response are not matching the UEM user.

Re: Workspace ONE - Okta Integration Part 3: SCIM Provisioning

StevenDSa — Thu, 18 Jun 2020 20:19:20 GMT

You are correct that in order to provision users from WS1 Access to UEM you don't need to complete those steps, however they are important for other aspects not related to the provisioning.

Here are some key things, make sure under Directory Services in UEM that NONE is selected for the directory (at the top OG) and SAML is configured.

Also under Devices and Users -> General -> Enrollment, make sure the Directory authentication mode is enabled.

Re: Workspace ONE - AirWatch Provisioning App

StevenDSa — Thu, 18 Jun 2020 20:13:18 GMT

Hi Kw,

Regarding the first point, have you configured Hub Services to use Workspace ONE Access? You will also have to configure Directory Services (in UEM) to use SAML with Workspace ONE Access as well? This also means you will need to configure the AirWatch app inside of WS1 Access.

Regarding point 2. Please make sure in the A/W Provisioning Application that the OG specified is the top OG. Also, the groups you are trying to push from WS1 -> UEM, are these regular groups in Okta or assignment groups in Okta. This makes a difference. Okta does not support/recommend pushing the same groups that are using for assigning the WS1 application.

Re: Workspace ONE - Okta Integration Part 3: SCIM Provisioning

StevenDSa — Mon, 15 Jun 2020 20:58:07 GMT

Agreed that is not a helpful error. Did you follow my other blog on configuring the A/W Provisioning adapter? Workspace ONE - AirWatch Provisioning App

Fixing Group Issues for VMware Cloud Services Customers + Okta SCIM

StevenDSa — Tue, 15 Jun 2021 14:35:27 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

How do I see all the WS1 Access User Attributes?

StevenDSa — Tue, 15 Jun 2021 14:35:01 GMT

For updates on this blog and other blogs: Follow @SteveIDM

This blog has been moved to

https://TheIdentityGuy.ca

Re: Workspace ONE - AirWatch Provisioning App

StevenDSa — Fri, 17 Apr 2020 14:56:48 GMT

Strange. The only reason you should get this error is because SAML is not configured on the top level OG. Directory Type should be set to none. SAML should be configured for at least Enrollment and SSP. Also Directory Type should be checked off in Devices & Users -> General -> Enrollment.

If that doesn't work I suggest you contact VMware Support.

Re: Workspace ONE - AirWatch Provisioning App

StevenDSa — Fri, 17 Apr 2020 14:47:24 GMT

And you are doing this on the top level OG?