Strange query parameters in SCIM v2 push

I created an Okta application to test my SCIM provisioning to an app, and I am receiving GET requests to my app that seems to have bad query parameters /api/scim/v2/Users/?startIndex=1&count=100-f8153e2ef0c4. This request looks malformed to be based on how I’ve read the SCIM 2.0 spec, not to mention I don’t know where the -f8153e2ef0c4 part after count=100 is coming from. I’d expect the request to look like /api/scim/v2/Users?startIndex=1&count=100. Has anyone seen something like this before? It seems unlikely that I misconfigured something to cause this (I didn’t change much from the defaults), but I don’t know for certain.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.