Artificial Intelligence (AI)
Big data analytics with Starburst
Secure from Code to Cloud
MITRE ATT&CK (tactics, techniques, matrix, IDs)
Prisma Cloud in 60s
Changed focus – The world of…
Horizon – Brokering
Horizon Golden Master – Best practice
Horizon Cloud on Azure
Horizon Cloud on Azure – How to start with subscription

Okta Group creation and application assignment with Workspace ONE

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 because then all users in that group will be deployed automatically to Workspace ONE UEM if they part of this group.

Caution: In case of using the SCIM provisioning (our case) to provision users and groups you will run in an issue on the Workspace ONE Access side. If you create a group in Okta and provision / push it via group push and SCIM to Workspace ONE Access that created group will be associated with the System Domain of Workspace ONE Access instead of the createddomain ( for instance) which we created to provision users to.

Reason behind that issue is that the Okta SCIM request to create a group don´t contain the domain attribute which is associated with the correct domain (directory) which we created before and exists in Workspace ONE Access. Unfortunately, the SCIM request to create a group in Okta can´t be customized to contain that attribute.

But good news, we can work around that. We will use Postman again.

Caution: That is only possible in case the application (Workspace ONE) in Okta is able to use unlink and relink again. In my testing it don´t worked well but to have a full overview of what is possible. Maybe it helps in another scenario. Will give it a try again later 😉

  1. Open Postman
  2. Open a new tab (or maybe you have the old one still open from create Bearer token)
  3. HTTP methodchoose Post
  4. Enter the url: https://tenanturl/SAAS/jersey/manager/api/connectormanagement/directoryconfigs
    • Replace tentanturl with your Access tenant url
  5. Check that the authorization header is OAuth 2.0
  1. Under Headers set Content-Type to application/json
    • Make sure if you use the old tab from Bearer token creation, that you disable the Content-Type entry from that (application/
  1. Now we create the group in Workspace ONE Access which will be later associated with the group we will create in Okta. As follows an example, please replace:
    • DisplayName = the Name of the group in Okta (you will create it or have it done)
    • Domain = the domain we previously created in Workspace ONE Access for Okta


"displayName": "Okta_Users",

Please be aware of the syntax.

You should see like this:

Now you can see in your Workspace ONE Access administration console the created group (Okta_Users) which is associated with the created Directory and domain for the Okta SCIM provisioning.

Now we have to (can) create the Group in Okta and make the users a member of that.

  1. Log into your Okta tenant
  2. Directory
  3. Groups
  4. Add Group
  5. Choose a name and description
  1. Add Group
  2. Manage People
  3. Add the members
  4. Application tab
  1. Same procedure as for users, assign the Workspace ONE application to the group for provisioning
    • BUT, one additional step here
  2. Applications tab at the top
  3. Applications
  4. Assign the applications you want (Workspace ONE for instance)
  5. Tab Push Groups
  6. In the green box Push Groups click the arrow
  7. Find groups by name (you can choose what you want)
  1. Type in your created Group in the search box
  2. Check the box Push group memberships immediately
  3. Save
1203 Total Views 1 Views Today

Leave a Reply

Your email address will not be published. Required fields are marked *