SCIM Get User error 400

Description
Zoom SCIM API returns error 400 when Azure sends an initial request.

Error
Normally Zoom returns a message with status 200 after Azure send a test request before account provisioning. Starting from today, zoom returns status 400, making azure stops provisioning.

Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT SCIM user API

Which Endpoint/s?
scim/Users

Call log before:
{
endpoint: “https://api.zoom.us/scim/Users”,
response_headers: [
“Set-Cookie: zm_aid=”"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly"
],
date_time: “2020-04-19 15:42:13”,
method: “GET”,
request_body: “N/A”,
response: {
schemas: [
“urn:ietf:params:scim:api:messages:2.0:ListResponse”
],
totalResults: 0,
startIndex: 1,
itemsPerPage: 0,
Resources: [
]
},
request_headers: [
“authorization: ******”,
“connection: close”
],
request_params: [
“filter: userName eq “AzureAD_Test-abf00683-c088-474a-a15e-07c35f3eb29d””
],
http_status: “200”
}

Call log after:
{
endpoint: “https://api.zoom.us/scim/Users”,
response_headers: [
“Set-Cookie: zm_aid=”"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly"
],
date_time: “2020-04-19 15:49:29”,
method: “GET”,
request_body: “N/A”,
response: {
schemas: [
“urn:ietf:params:scim:api:messages:2.0:Error”
],
detail: “User AzureAD_Test-36bf9236-1ff7-432d-8375-6830f741cb61 not exist or not belong to this account.”,
status: 400
},
request_headers: [
“authorization: ******”,
“connection: close”
],
request_params: [
"filter: userName eq “AzureAD_Test-36bf9236-1ff7-432d-8375-6830f741cb61"”
],
http_status: “400”
}

I’m getting the same error. Please investigate Zoom.

Hi, this error started for us as well for first time on Apr 19 at 07:47 AM UTC, and Azure provisioning is now quarantined

Hi @TcChung @hsheppard & @it-procurement, we’re investigating this, I’ll get back when we have an updated.

1 Like

Seems to be working again for us. I assume this is related to throttling being introduced on the API on 19th April.

1 Like

Happy to hear it is working @it-procurement! :slight_smile:

Please let us know if you experience additional issues.

Thanks,
Tommy