-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auth state is not persisted in ClientStorage #40
Comments
@dstendardi This could be something else, such as logging into your Auth0 app using a social provider's development keys. See Limitations of Developer Keys. Failing that, have you already tested that being able to ignore the cache fixes your issue? |
@dstendardi are you talking about your app's session or the Auth0 session? If you're talking about the Auth0 session, then what @stevehobbsdev said makes sense. If you're talking about your app's session, then this is by design. Nothing is persisted locally. Each time you initialize the library ( |
@luisrudge How can I retrive token object in angular spa (access_token, expires_in, id_token, token_type)? When I call await this.auth0Client.getTokenSilently(), I've got only single access token. |
@luisrudge and @stevehobbsdev You are right this is a limitation of development environment and google login, classic login/password challenge works fine. 👍 |
@GazerSpectre you don't have access to the raw response, but you can get all the information via the
|
@dstendardi because when you init the library, you'll never have anything cached, since we only use in-memory cache. |
Description of the problem
Every time page is refreshed, session is lost and user need to re-authenticate.
Proposed solution
In index.ts, allow user to ignoreCache or not by passing option :
If this suggestion makes sense, i can open a pull request for it, let me know !
The text was updated successfully, but these errors were encountered: