Brett Ritter

Internal ref: OKTA-306433

@jeremyhermann - no progress to report yet, but I'm requesting to bump this up in priority.

@jeremyhermann @kuehlein - I did more extensive testing, and I've been unable to replicate the problems you describe (react 3.0.2 changed some details about SecureRoute - that may have resolved...

@jeremyhermann @kuehlein - We found an issue with SecureRoute, and addressed them with @okta/okta-react 3.0.5. Please try it out and see if the problems you reported still exist.

Internal ref: OKTA-306433

`@okta/jwt-verifier` currently only verifies tokens from Okta Custom Authorization Servers, which does require API Access Management. If you are using Okta Org Authorization Servers (which don’t require API Access Management)...

@jraadt - Thanks for your investigations, particularly the code snippets. We look into issues as priorities allow, so your efforts are helpful and appreciated.

@bdruth - Thanks for the question, I'll forward this to team members that can speak intelligently about react-native and see if we can get you an answer.

> My initial expectation was that it means: authentication flow is currently running @patkovskyi - Close, but not quite. `isPending` means "We are currently figuring out what your authorization is"....

@sero323 & @lee-bennie: We do not have a solution at this time, but the team is reviewing priorities today and I'll see if we can get this bumped up. Meanwhile,...