Bug: Client authentication with confidential access isn't working about react-oauth2-pkce HOT 6 CLOSED

can be closed

from react-oauth2-pkce.

I might be missing something in the description, but I think this would be easier to debug if you added some of your code to the description, so that we can see exactly how you've used the library. That will help us see if the error is on our end, or if the code needs to be tweaked.

I'd recommend simplifying the code as much as you can (while still retaining your error), to make debugging even easier. Feel free to replace your personal keys etc. with e.g. <KeyCloak ID>.

from react-oauth2-pkce.

i use the example code without any changes just the demo code.

from react-oauth2-pkce.

then i turn off confidential acces it works with the demo if i turn it on it doesn't. i have signend out ther session in keycloak manually to chek if this would change something. but it doesn't.

from react-oauth2-pkce.

Hi @eriCCsan
Do you have any documentation stating that Keycloak supports using a client both as a public and a confidential client at the same time?
I really think the issue here lies with how you are using Keycloak.
There isn't really anything we can do on the client to manipulate this. If you still think the issue is with the client library, I would need some more information on what is expected by Keycloak that is outside the OAuth2 spec

from react-oauth2-pkce.

well i figured out that keycloaks approach for this is to use two client and map the things from the other client into the token. that would solve my problem. The funny thing is that no one on any documentatzion said this would not work so i assume it would work.
As @soofstad already i think too it would not be possible to have kinda function in one client

from react-oauth2-pkce.