by Mike Gruner
In the life of a technican it´s always important to be aware of the best practices. In case of VMware Horizon, I´ve done a lot sizing and design, been on a lot discussion around that topic and wants to share a pretty
Okta GUI HTML As I configured the last time an Okta integration with Microsoft Azure and Office 365, I recognized a bug in the administration console if you want to configure the integration with the option of Okta password sync. The configuration
Check Attribute mapping – Okta To make the whole process works if you implemented the compete scenario (Workspace ONE Access and UEM, Okta and Microsoft Azure) we have to make sure that the user attribute mapping is correct. So, you have to
Integrate Workspace ONE in Microsoft Azure AD If you want to use Microsoft Azure AD as well with Workspace ONE we have to configure some things here. First of all, we will integrate the AirWatch MDM application into Azure AD that we
Now I will describe how you can handle Group creation within Okta and make sure it will be associated to the correct Directory. Create Okta Group to synchronize to Workspace ONE Access To be more flexible I recommend using a group assignment
If you want to use your assigned applications from Okta directly from the Workspace ONE Access console we have to integrate Okta as an application source in Workspace ONE Access. After the configuration the applications which the users were assigned to in
Integration of Microsoft Azure AD and Office 365 in Okta As next we integrate Microsoft Azure AD into Okta that we can provision users from Okta to Azure AD as well. In that case we can use two scenarios of integration, Password
Integration of Microsoft Azure AD as Directory Services in Workspace ONE UEM In case you want to integrate a Directory Service in Workspace ONE UEM for instance Microsoft Azure AD you can do this as follows. Log into Workspace ONE UEM Groups
Integration of Workspace ONE Access as 3rd party SAML iDP in Okta We can integrate Workspace ONE Access as 3rd party SAML iDP in Okta. That is necessary for the Device Trust Use Case for instance with iOS and Android mobile devices.
In case you want to use Enterprise Mobility Management or Modern management for your devices as well and additionally use the configuration as described before to let the users authenticate against Okta first before they can log into the Workspace ONE platform,
You cannot copy content of this page