openid-configuration Repeat request

[Buried-Love]

When I log in, I log in successfully for the first time,But the VM requests againopenid-configuration. Cause me to report an error :
ResponseValidator._processSigninParams: Response was error login_required
openid-configuration The first request was made by oidc-client.main.js issue. The second request was made by VM.

please help me... thank you!

[guillaume-chervet]

Sorry, we have a bug in version 3.1.7, you may retrograde to 3.1.6. It should work better.

[Buried-Love]

Sorry, we have a bug in version 3.1.7, you may retrograde to 3.1.6. It should work better.

Thank you for your reply ! It's the same problem after switching versions.

[guillaume-chervet]

Do you have the problem with exemples on that repo?

[Ansalibrahim]

I am using v3.1.6. It occurs in the incognito mode of chrome. And it happens in example too (context).

[Ansalibrahim]

I can confirm that this happens in all versions @3.1.+.

[Ansalibrahim]

The error is occurring inside the dependency oidc-client and it is deprecated 🤦‍♂️

[jafin]

@Ansalibrahim yes refer to #641 re deprecation

[Ansalibrahim]

@jafin Have you found any workarounds or anything of that sort?

[Ansalibrahim]

Here is the available log... just before this log, I signed in and 2 seconds later I got signed out.

[Ansalibrahim]

@Buried-Love Have you found any solutions?

@guillaume-chervet Could you help to workaround the issue?

[robertmadril]

Hello,

This issue was encountered while utilizing the HOC implementation of OidcSecure in react-oidc-context. The same logging output as described in previous posts were encountered while on version 3.1.6 and 3.1.7.

In order to bypass this, custom auth logic was implemented in the application which calls for the user via userManager.getUser() and determines the authentication route utilizing the login() functionality exposed by the useReactOidc hook exposed from the library.

However, please inform if anyone else has found an effective solution without having to use custom logic in the application code.

[allemas]

Hello @robertmadril :)

Could you share an example? I'm afraid to do this wrong.

[guillaume-chervet]

The coming v4 will fix this. The alpha is fonctionnal but I need to document it and Write à small migration guide.

[allemas]

How can we help you to do it? Did you open a milestone?

[guillaume-chervet]

Thank you for your answer. I do not know what is a Milestone. If you Want you can copy this branch https://github.com/AxaGuilDEv/react-oidc/tree/feature/v4
I have more test and documentation to do. Some feedback would be great. There are required breaking changes.

[TeckTn]

Is there any plan to upgrade oidc-redux package to v4 also?

[guillaume-chervet]

Unfortunately i am not using redux any more in my current projects. I think that the vanilla oidc behind v4 is quite simple to use with redux. It would be great if someone could have the time to write a small redux wrapper.

[TeckTn]

Thank you for your response and for this magnifique repo.
Unfortunately am not enough skilled to make a pr for now.
I will just migrate to vanilla js.

[guillaume-chervet]

v4 context version does not really use context (I will remove it).
It may be already redux compatible.
https://www.npmjs.com/package/@axa-fr/react-oidc-context/v/4.0.0-beta.9

[guillaume-chervet]

I close the pull request. Feel free to reopen it if you need it.
Thank you very much. I think the v5 is simpler ans resolve that problem and is full compatible with a react redux architecture.