pamapa
pamapa
Thanks for contributing!
Thanks for contributing and being patient!
> actually, with 3.0.0 version it seems to be working good to know
> I assume the wrapper is needed to update the state and trigger reflow, but why it's not thrown back? In contrast to `oidc-client-ts` this library manages an `error` state,...
> However, clicking Sign Out I am redirected to OP /logout. If I then navigate back to the React SPA, when I click Sign In I am automatically signed in...
Very true, in case you can not protect a `client_secret`, e.g. when running on a client on customer side like browser. Do **not** use `client_secret`. The preferred way to use...
> the authentication provider in question does not support PKCE code flow. This library and the underlying library has a strong focus on PKCE code flow, respectively on OAuth2.0. I...
> Does this library use PKCE by default (meaning do the code examples in your README essentially create an Authorization Code w/ PKCE flow by default) or are there other...
> Where and how do I set these (the Code Challenge and Code Verifier) in `react-oidc-context`? They are part of the underling library. Have a look at [oidc-client-ts](https://github.com/authts/oidc-client-ts). e.g. https://github.com/authts/oidc-client-ts/blob/main/src/utils/CryptoUtils.ts
> Thanks again @pamapa , so just verifying, it looks like there's nothing I need to explicitly set, this library will generate and send Code Challenges/Verifiers automatically for me using...