Guillaume Chervet

Hi @AnimaLupi, thank you very much for your nice issue. In good REST API design server is responsible to manage HTTP cache. Theoricately, the openid-configuration can change and the client...

I reopen the issue to trace the client cahe development need. Thank you very much :)

Hi @AnimaLupi , we have added some cache in v6. Now we have less call to oidc server configuration.

Thank you @drue66 , I'am very sorry for that bug. In fact there were 2 bugs => https://github.com/AxaGuilDEv/react-oidc/commit/06d02a920cd0845a2f151fc2bdb926d611aa3ac8 last version fixed it. Thank you again !

Hi @AnimaLupi @drue66 , i close this issue and I keep #819 for enhancement. Thank you very much for the issue and your feedbak.

Hi @frogerdevs thank you very much for your issue. Does the flow work if the configuration is valid from the beginning? When you are stuck, do you have an error...

I found a way to reproduce it but i do not know how to fix it yet ^^

Does the version 5.10.1 fix your issue? It is a bug quite hard to debug ^^

Thank you for the feedback @frogerdevs . I will make some tests again today.

I suspect it is link to service worker, because sometime a response promise is never resolved. I am making test all day long but I dont find it.