In many of the SCIM integrations we have with various partners, they typically require a bearer token for user provisioning into Workspace ONE Access. In an ideal scenario, we would like to use an Authorization Code Grant flow for SCIM integrations however that is not always possible. In Workspace ONE Access, each customer has their … More How to limit the scope of a SCIM Bearer Token
I’ve had quite a few requests lately for assistance setting up SCIM capabilities with OneLogin and Workspace ONE. In full disclosure, I’ve set this up in my lab but I’ve not done full end to end testing of all CRUD capabilities. The one obvious difference in the setup and configuration with OneLogin over some of … More Using SCIM with OneLogin and Workspace ONE Access
There are times during troubleshooting where you like to see a particular attribute in Workspace ONE Access and its not displayed in the web portal or times when you would like to update a particular attribute or delete a JIT user. DISCLAIMER: Please use the API with caution as this can potentially cause issues if … More Using Postman to Manage Workspace ONE Identities
In Workspace ONE Access, you might have configured additional attributes and would like to populate those attributes from your source of truth such as Okta. Perhaps its a single attribute: Or maybe you have many attributes: When these attributes are created in Workspace ONE Access, they are created in a custom schema. The schema is … More Extending the Workspace ONE Application in Okta for Additional Attributes
If you are a VMware Cloud Services Customer and you are trying to use the VMware Workspace ONE application in Okta to leverage SCIM management of identities in WS1, you might be running into an issue with Groups. In Workspace ONE Access you will notice that groups created from Okta are associated with the System … More Fixing Group Issues for VMware Cloud Services Customers + Okta SCIM
Steve The Identity Guy 