statusCode 400 on API Request - Bad Request - Client Secret

[aaron.rose]

Afternoon Team,

Could you please assist with an urgent issue we are experiencing with our 3rd party application integration into SimPRO?

We are currently experiencing statusCode 400 errors regarding bad requests made through existing integrations into our other 3rd party applications via the API. We have a variety of applications that have integration with our SimPRO suite which use different credentials and platforms that are all impacted.

The body of the POST request is:

Request URL:
https://<company>.simprosuite.com/oauth2/token

Request Body:
{
"grant_type": "client_credentials",
"client_id": "client id",
"client_secret": "client secret"
}

A copy of the response below:
Response from /oauth2/token with our previously generated credentials is
{"error":"invalid_client","error_description":"The client credentials are invalid"}

Please note - this impacts all existing client secrets, however, we were able to create and use a new one without issues. We appreciate your swift response and guidance as this has impacted BAU. Please advise on how we can open a line of communication to get this rectified.

Are you aware of any issues with this function?

[Sindre]

Hi aaron,
Have these integrations worked fine earlier using the same code to authentice?

The tokens received are valid for one hour, could something be wrong with your code fetching a new access token?

Can you try the same authentication method using your credentials in an API tool such as Postman to see if you receive the same errors?

Regards

[aaron.rose]

The code has not be altered between being functional and non-functional. This is quite surprising to multiple departments. We have SimPRO integrations with Microsoft, JIRA, and other services, including tests in postman that are all impacted. As mentioned, the requests are fine when creating new client profiles to run as. It's as if something has happened to our existing connections.

Hi aaron,
Have these integrations worked fine earlier using the same code to authentice?

The tokens received are valid for one hour, could something be wrong with your code fetching a new access token?

Can you try the same authentication method using your credentials in an API tool such as Postman to see if you receive the same errors?

Regards

[nige]

Hi aaron

we have responded to you directly by email.

Regards