Hello and thanks for reading.
I’m developing a SCIM API for our external application. When creating a user in our application, we require a RegionId.
However, this ID is specific to our application. The Okta user will have a region assigned, but it will be the region’s name, so it’ll need to be mapped to its ID before being sent in SCIM requests.
Is there a way to store these mappings within Okta and perform a lookup when sending the requests?
If so, is it possible to automate this list using an API endpoint? We have an endpoint that surfaces all region names and IDs. Optimally we could call this regularly, or with each request, to make sure the mappings are up-to-date.
An example of what I’m trying to achieve:
User is created in Okta with a region of “Eastern”
“Eastern” region name is replaced with its corresponding ID, either by using a static lookup table, or by calling an API and evaluating the response body.
The SCIM “Create User” request is sent to our external application, including the RegionId.