
v792b (v792b) asked a question.
Hello! I'm trying to connect my own server implementation of SCIM 2.0 API to Okta using Bearer Token Authentication, and have been testing the connection in the setup using the Okta SCIM client. However, I've been getting a strange error where the Okta client is getting ids of users that don't even exist in the list of users that I got my bearer token from. When I test my API on Postman, it works. This call /api/v2/scim/Users returns all the users that exist, and it seems to work when called from the Okta SCIM client, but it's getting the wrong users? I try to assign a user to my Okta application, and I see on the logs for my service that it's calling the read_user endpoint - /api/v1/scim/Users/u-0000000000138 (fake user id) for example, but this id doesn't exist when I make the same call and check all the users through Postman. I have no idea how the Okta client is getting these different user ids. Any assistance would be appreciated!

Hello Agnes,
I will be assisting you, please allow me some time to look into similar issues and i will update you with any new information.
Hi Agnes,
I was not able to find anything related to this issue. Please open a support case as this may require in depth troubleshooting.