AlexB.37951 (Customer) さんが質問をしました。
/api/v1/users API case sensitivity
There is some inconsistency with how the users API handles the casing of profile.login for filtering versus creating new users. I have an existing user in my org with login of User@example.com and I'm building up some API requests to work with that user as user@example.com Here's a session for trying to find user, not finding, but failing when user is being created. GET https://example.oktapreview.com/api/v1/users?limit=1&filter=profile.login%20eq%20%22user@example.com%22 HTTP/1.1Authorization: SSWS (snip)Accept: application/jsonHost: example.oktapreview.com HTTP/1.1 200 OK(snip headers) [] --- POST https://example.oktapreview.com/api/v1/users?activate=False HTTP/1.1Authorization: SSWS (snip)Accept: application/jsonContent-Type: application/json; charset=utf-8Host: example.oktapreview.com {"profile":{"login":"user@gmail.com","email":"user@example.com","firstName":"?","lastName":"?"},"credentials":{"password":{"value":"(snip)"}}} HTTP/1.1 400 Bad Request(headers snip) {"errorCode":"E0000001","errorSummary":"Api validation failed: login","errorLink":"E0000001","errorId":"oaeBPlwzzB_QNGk7KjLslUO2Q","errorCauses":[{"errorSummary":"login: An object with this field already exists in the current organization"}]} It would be nice if either GET/filter were not case sensitive or POST were.
- GET {org}/api/v1/users/{username}