Oidc-client-js: Not working in firefox.

[mvrhov]

The version in master is not working in Latest version of Firefox. (It doesn't matter which mode do you use Private or normal)

I'm looking at the user-manager-sample.html example.
The way i'm testing this is:

• start signin main window
• end signin main window
• signin with iframe

In Firefox after clicking on sign in with iframe I'm either getting "No state in response" or "Error: No matching state found in storage" (sometimes you have to hit the signin with iframe button 2nd time for this to happen) I've tested this in both Windows and linux versions of FF

edit: It's the same when using identityserver-sample.html

No node here, so the above is run in such way that the nginx is pointed to the folder containing the files.
So the final url looks like http://servername/oidc-client-js-dev/samples/VanillaJS/public/identityserver-sample.html

[brockallen]

I am also getting Error: login_required from the iframe in FF. I'll look into it.

[brockallen]

I am also getting Error: login_required from the iframe in FF. I'll look into it.

Ok, this was a red herring -- I had my privacy settings so cranked up that FF was blocking the cookie sent in the iframe.

Once I relaxed that setting, then it was all properly. So in short, I can't repo your issue.

[mvrhov]

My firefox settings are set to default. At least for the Linux version I'm 100% sure. as I have just installed it and not touched any settings.

[brockallen]

So then I will need to you do some more investigation. It might be environmental.

[brockallen]

Any update on this?

[mvrhov]

From my side no. But I do know, that the slient login fails pretty constantly in both FF and Chrome. To the point that it is almost unusable.

[brockallen]

Well, your report is the only one, so as I mentioned before it will require more investigation on your side I think.

[anwalkers]

@brockallen @mvrhov I am getting the same error in both firefox and edge. It only happens when storage has not been established. On our site you can open a "Private" window in edge or firefox and replicate the issue.

We are getting stuck in our callback.html. The token is returned in the URL parameters from identity server and I know it is getting stored, since you can change the URL back to the originally requested site URL and it will load without issue.

Unhandled promise rejection Error: "No matching state found in storage"
processSigninResponsehttps://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:3:7487shttps://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:46:120812Ihttps://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:46:120957chttps://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:1:42243 oidc-client.min.js:46:121192
B/</e<
https://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:46:121192
Oidc</t.exports
https://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:3:15616
B/<
https://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:46:121069
Oidc</t.exports
https://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:3:17677
<anonymous>
https://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:1:43043
m
https://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:1:42888
S
https://site.blank.com/vendor/oidc-client/dist/oidc-client.min.js:1:42908

[brockallen]

If storage does not work, then there's not much I can do to solve this. We need some way to maintain state across the authorize request & response.

[fa10]

I am experiencing the same issue on Firefox browser in private mode.

[brockallen]

I just tested private mode in chrome, FF, and edge and they're all working.

[brockallen]

Any update on this? If not, then I would like to close this issue.

[anwalkers]

@brockallen The issue manifests itself differently on different machines in different browsers. When I find a reproducible test case I’ll submit a new issue. I would close it. My guess is a timing issue...

[brockallen]

Ok, thanks for the update. If you can find a consistent repo, let me know. Thanks.

[dominikguhr]

hi there. @anwalkers @brockallen I am experiencing the same issue, mostly using incognito/firefox. Any new updates on this? It seems the localStorage doesn't get created at all when the error appears, but on my machine its very hard to reproduce the error (haven't had it for a while), although a colleague of mine gets the error nearly 80% of the time, which makes it unusable for him at the moment. We're now thinking about switching client library due to this error, which would be sad imho, but I just can't figure out a reproducible environment to narrow it down.

[Pinguwien]

I analyzed a little further, but without success for now. Thought about having something to do with creation of localStorage / sessionStorage in inkognito mode in ff, but no, as you can see... (oh well, btw, "dominikguhr" is just my other account which I accidentally used). Tested it with the feature detection snippet from the mdn article:

seems the storage itself is at least available... hum. out of ideas i am. help i need. ;)