This repository has been archived by the owner on Oct 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 232
SecureRoute does not give protection when used with render #808
Comments
Example working code:
That redirects me to Okta login. |
Having the same problem - this may be a duplicate of #724 that should be fixed in 3.0.2 https://github.com/okta/okta-oidc-js/releases |
I'm facing this same issue, 3.0.2. Component specified in |
The same is true if using |
Internal ref: OKTA-306439 |
|
Still unable to use |
Hey folks - this is on my immediate backlog, so while I can't say exactly what day this will be addressed, it should be Real Soon Now ™️ |
14 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey all,
I am building some components on top of your
okta-react
. I have found one issue.When I use the component like this:
It does not run
RequireAuth
at all. Therefore it will render without any auth checks.okta-oidc-js/packages/okta-react/src/SecureRoute.js
Line 44 in 28ed8e3
I created my SecureComponent where I fixed it like this:
Version: "@okta/okta-react": "^3.0.1",
Am I missing something?
The text was updated successfully, but these errors were encountered: