We built an API server to support SCIM 2.0 endpoints and tested it fully with Runscope and in fact managed to get resources once in Insonmia/Postman/cURL. But when we get a request from Okta the body is empty. Does anyone have a glue on what might be going on?
I’m experiencing the same thing.
Has this been solved? How?
I wasn’t handled the header application/scim+json properly so made some adjustments on my nestjs application and works.
Thank you for that!
For context:
Postman, Runscope, etc. (by default) they send content-type: ‘application/json’
While Okta client sends content-type: ‘application/scim+json’
As mentioned above, your application needs to handle/parse type ‘application/scim+json’
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.