David Lozzi
David Lozzi
I'm getting the same issues, seems more prevalent since we moved to a custom tokenManager for saving to cookies, and almost always happens in IE11 (yuck I know). Looking at...
@aarongranick-okta agreed, I thought it was related but determined it's unrelated. We just deployed the latest from 3.0.4 to 3.0.8 and am now seeing these issues. Our deployment servers clear...
> Make sure that you are using the latest version of `okta-auth-js` as we have released some fixes for this logic. If you are using an SDK like `okta-angular` or...
@aarongranick-okta thanks for the details, when do we think the PR for 3.2 will be ready for consumption? That fix looks promising!
@aarongranick-okta is this included in the React library as well? I see that's still on 3.0.8
@shuowu i just ran through it all, still getting the same error for anyone first time coming into our app. confirmed package-lock has the latest: ``` "@okta/configuration-validation": { "version": "0.4.3",...
in addition, it does work if we just try it again, every time. When we get the error, I can jump back to the URL we wanted, and it redirects...
I added something similar, let the user specify the names as needed, in PR https://github.com/MisterPhilip/omnibug/pull/78
Ditto. Please fix, related to https://github.com/wrakky/react-html-parser/issues/45
I got a valid workaround working... ``` renameProp = (oldProp, newProp, { [oldProp]: old, ...others }) => ({ ...others, [newProp]: old }); render() { ... const htmlOutput = ReactHtmlParser(htmlData, {...