I am currently facing an issue with the PAT which is returning “Bad credentials” when trying to generate access token.
However, the PAT was working fine for last 2 months and was used in integration with Powershell SDK to use cmdlets as below:
get-idnaccesstoken
get-transforms
But since last week, it is failing with below error.
Also, I am not able to access my tenant using VS code.
It simply looks like your client credentials have been deleted or you are using wrong secret. Check if you still can find them in the tenant, and if you can’t, then create a new set of client id and secret
Sadly, the simplest explanation is not the answer here.
It’s occurring at the tenant level (so it seems), for multiple IDN users with their own PATs. Issue started on the same day for Mandeep and myself, and another user…
We have a ticket opened for this, Support is scratching their heads too.
That would just be a ‘workaround’ as it doesn’t address why it occurred. Meaning it may reoccur again, unannounced, causing service interruption in a production environment.
With this in mind would there be any other restrictions within your environment, trying a connection from postman may help to narrow down the cause…
Looking into that…
I guess you should open a support ticket.
If you having issues on tennant level. Now check the PAT of you environment and be sure it was not deleted.
Already stated that we do have a ticket.
Lol trying to help´, no need to be mad.
Not mad. Just stating it’s been mentioned.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
