When running this example project locally with an instance of Identity Server 4 as the identity authority, it works fine in Chrome and Edge (on Windows), but Firefox for some reason adds an iframe into the markup a few seconds after the user is authenticated with src set to the connect/authorize endpoint. This causes an error on the identity authority's side ("No user present in authorize request") which in turn causes the React app to behave as if the user has signed out, even logging "Action type: redux-oidc/USER_SIGNED_OUT" in the console.
This is Firefox 59.0.1 (64-bit).
Why does Firefox, and only Firefox, add this iframe to the markup? FYI I've also logged this on Stack Overflow with more detail here:
When running this example project locally with an instance of Identity Server 4 as the identity authority, it works fine in Chrome and Edge (on Windows), but Firefox for some reason adds an iframe into the markup a few seconds after the user is authenticated with src set to the connect/authorize endpoint. This causes an error on the identity authority's side ("No user present in authorize request") which in turn causes the React app to behave as if the user has signed out, even logging "Action type: redux-oidc/USER_SIGNED_OUT" in the console.
This is Firefox 59.0.1 (64-bit).
Why does Firefox, and only Firefox, add this iframe to the markup? FYI I've also logged this on Stack Overflow with more detail here: