Thanks for the clarification, @punisher660.
I’m not sure what could be causing the issue here, but you try using the oidc debugger playground as explained here - Get an access token manually for testing
That won’t fix your issue but will give you confidence in your configuration.
Also, I have a feeling that your issue could be related to following redirects. Is the response code you receive a 200 instead of 302? In that case, check if there’s a config to set “follow redirects” to true, while building your client.