Issue with HTTP Request Step: client_id Header Being Capitalized

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hey Guys!

We’re currently facing an issue with the HTTP request step used in our workflow.

The request is sent to a middleware and includes user data. For authentication, we rely on a header named client_id.

image
image305×229 9.17 KB

However, once the request reaches the middleware, the header client_id is transformed into Client_id. This change in capitalization causes the following error:

Could not find a required client_id in the request, identified by HEADER or QUERY client_id

Everything was working correctly with the header sent in lowercase until June 20th.

Has anyone encountered a similar issue or have any idea what might be causing this change?

Thanks in advance!

2

Are you implying that when it is received by the middleware that it is received as upper case, where before it was lowercase? Just trying to confirm if the change happened on the ISC side.

If you have a backup of your connector, it would be interesting to evaluate if there were changes on the connector itself. Was production and sandbox both impacted?

Is this production or sandbox? I have seen at times when the UI is modified on connectors in the past, we had some sandboxes that we had to update logic that was there previously. Not that this is the same by any means, just thinking that comparing the connector to a prior version is always a good idea and to take periodic exports.

3

Yes, it was received by the middleware as lower case and now it becomes receiving as upper case.

It’s not a connector exactly, i’m using a workflow with the http Request that request this api to the middleware

we haven’t changed anything, it appears it’s a sailpoint side thing

it’s a sandbox environment

4

Hi @gustavoesp_1337,
Try updating the client_id again in the workflow manually and then test and see if it works fine. ?

Thanks

5

Hey!

Just did it, it didn’t work :face_with_diagonal_mouth:

we get the same error
Could not find a required client_id in the request, identified by HEADER or QUERY client_id

6

I would request raise a Sailpoint Support ticket for the same.