Hello @swagata.sengupta
Thanks for the inputs!
I also dug a bit deeper into this problem and I wanted to share my findings.
First, I wanted to see what payload Kore was sending to the token URL, so I created a dummy token URL API so that I can observe the incoming requests. It seems that the correct payload is indeed being sent.
(Note that I generated new client ids, secrets and users so that I can share it in this forum)
Second, I tried to forward this request to our real token URL, just to see what the response was. To my surprise, the request went through!
Thus, for now, I have a workaround :). However, I still have no clue why Kore can’t use OAUTH2 directly to our identity platform. Additionally, this platform is being maintained by a separate team on the other side of the world – hence I have no way to get the error response from the logs.
If someone from Kore wants to replicate this, I can post the oauth2 details here. I will also report this issue to our team that maintains our identity platform.
@vijay.thakkar - If you don’t have access to your identity platform logs, you can follow what I did. First, use a dummy token URL just to check the incoming request. Then, you can then forward it to the real token URL to see what the real server response is. Kore only shows a generic “Failed to obtain access token” message, hence it is hard to get the real error response from the identity platform.