Aaron Granick

@adammo94 Try using the `render` attribute on the route instead of `component`, the behavior is described here: https://reactrouter.com/web/api/Route

@adammo94 OK, I think I understand. You would like to have some UI that shows on all secured routes, but does not show on unsecured routes. The way it is...

@adammo94 Several routes, including "/" have plain attribute `exact`. I think it needs to be `exact={true}`. Also I do not think you want all your routes as children of `

internal ref: OKTA-408692

@niskah-energies The current version of `okta-angular` does not pass any parameters to the `isAuthenticated` function. We are working on a new release which will pass the `authService` as a parameter;...

@lawchihon This is a known issue with the latest version of Chrome. We have fixes in the latest versions of our modules. If possible, update to `[email protected]`. To continue using...

@alexspence What version of IOS? Have you tried it in the XCode device emulator, and if so, does it reproduce there?

@tek-bkarimi It's possible this issue is related to "secure" cookies. By default, this option is enabled, but it can be disabled by setting: ``` cookies: { secure: false } ```...

@m-lehti We believe that any issues with the OAuth redirect params cookie were fixed in 3.2.5. In fact, we have changed the error message so if the message still says...

@m-lehti Are you including the okta signin widget in your app or are you redirecting to Okta for signin?