LighthouseMike | 2024-02-20 15:05:45 UTC | #1
Good morning,
I'm sure this is a question as old as the hills and very noobish of me to ask, but after plenty of research, including asking an AI, I haven't been able to arrive at an explanation, much less a solution. Here's what I do know:
- Yesterday, everything worked fine.
- My org, client ID, and region haven't changed since yesterday (the only forum post on the subject was about someone who had the wrong region).
- None of the code that reads our API credentials has changed since yesterday.
- AI was confused, thinking the error was not about the client ID itself, but rather an access token (but the error didn't say that, and I've cleared my browser cache so AFAIK it never gets an access token).
- My best guess is that it has expired, but there is nothing in Genesys Cloud (at least, not where I'd expect to find it, in Integrations > OAuth) saying it has expired or offering any sort of renewal interface.
Anyone else ever rammed their head into the wall on this one? :laughing:
tim.smith | 2024-02-20 15:11:24 UTC | #2
That error means at least one of these things:
- the client ID being used doesn't exist in the region you're trying to authorize in
- someone deleted the OAuth client from your org
- you have a typo in your client ID
LighthouseMike | 2024-02-20 15:26:57 UTC | #3
Thanks for the quick response! :smiley:
the client ID being used doesn't exist in the region you're trying to authorize in
We know that's not the case, because the client ID and region haven't changed since yesterday.
you have a typo in your client ID
We can rule this out as well, because (again) it was all working yesterday and hasn't changed since then.
someone deleted the OAuth client from your org
This was my first thought, and at the moment the only lead I have. I guess I'll have to create a new one and see what turns up. Thanks again.
LighthouseMike | 2024-03-05 17:11:38 UTC | #4
Quick update on this - just in case anyone else runs into this problem - in my case it turned out to be something that broke in my encryption key (I won't go into details, for obvious reasons). So I had to re-key my a few things and it worked. So if you're reading this a few months from now or later,a nd you're doing any kind of two-way encryption of client ID/secret, just know that can be a factor as well.
system | 2024-04-04 17:12:35 UTC | #5
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 24750