Hi guys,
I’m testing the Airwatch provisioning app (and airwatch app). I’ve followed this video from Peter Bjork. The users getting provisioned from Access into Workspace UEM but when I test the self-service I’ll get an error:
SAML authentication has timed out; please try your request again.
I’ve tested an enrollment with an iPad with the same result.
If I test it without the SAML (disable SAML for Authentication option for Enrollment/Self-Service) with a basic account it works. Access and UEM are cloud based.
Anyone seen this before?
I think i found the answer.
I'm also testing with a different iDP (Okta) so you need to put that information here.
for those who want to know more, I came across this link that explains a few things clearly:
https://darrylmiles.blog/2019/09/16/integrating-workspace-one-uem-and-access-with-okta/
I think i found the answer.
I'm also testing with a different iDP (Okta) so you need to put that information here.
for those who want to know more, I came across this link that explains a few things clearly:
https://darrylmiles.blog/2019/09/16/integrating-workspace-one-uem-and-access-with-okta/
Hi,
I did a similar setup recently, but with google directory instead of okta.
We did a saml integration between google directory and workspace one access and then a saml integration between workspace one access and workspace one uem. We also use the airwatch provisioning app in ws1 access in order to provisioning users to ws1 UEM.
what I found in the airwatch application that are used for the saml integration between ws1 access and ws1 uem, we needed to have the deviceServices URL for the parameter "AWServerName" for enrollment and self-service-portal.
We followed https://www.vmware.com/pdf/vidm-airwatchapps-saml.pdf guide to integrate ws1 uem and access with saml.