Jared Perreault

If this problem persists you can try reaching out to https://support.okta.com/. They can help with setting up your org configuration to enable these flows

@IlanJana A breaking change included in the widget 7 release is the default engine is no longer "classic". Widget 7 requires you to "opt-in" to use classic engine via the...

If you haven't already, you can try reaching out to https://support.okta.com/. They can help determine if this is a code issue (problem with the signin-widget) or an org configuration issue

@kochste The most recent major version of SIW (v7) includes jQuery 3.6 (https://github.com/okta/okta-signin-widget/blob/master/packages/%40okta/courage-dist/package.json#L9)

@kelvin-chappell @Mark-McCracken Do you mind explaining your use case?

`okta-react` is a wrapper for `okta-auth-js` and provides a few conveniences for the React ecosystem, like `` and `SecureRoute`. It's completely reasonable to use `okta-auth-js` directly, instead of `okta-react` if...

@poddb which sample are you trying? `okta-hosted` or `custom-login`?

@poddb are you attempting to run this locally? Or on heroku? I just did a fresh install and the sample worked for me (locally) ```bash git clone https://github.com/okta/samples-js-react.git cd samples-js-react...

Does it crash if you go to `https://*******.herokuapp.com/okta-hosted-login`?

@poddb I created an internal ticket to look into this. The sample works fine locally, so it might have something to do with deploying to Heroku Internal Ref: OKTA-506911