-
Notifications
You must be signed in to change notification settings - Fork 232
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
Provide a synchronous way of retrieving the currently stored Credentials #437
Comments
Hi @JanC, we'll look into adding a way to retrieve the user profile separately from the credentials in the next major. This is unlikely to happen for the current 1.x. Will close this for now. |
thanks for your answer @Widcket
Even if I make a PR ? :) cheers |
We'll discuss this internally and come back to you. |
ok, I have a branch somewhere with pretty much the implementation I posted in my original comment. I'll clean it up + write tests and will submit a PR. I'll look at the UserInfo |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇♂️ |
Describe the problem you'd like to have solved
Hey,
as a SDK user, I'd like to retrieve the currently stored
Credentials
in a synchronous way so that I can access some metadata stored inCredentials.idToken
regardless of the credentials validityDescribe the ideal solution
In the same way
Auth0.CredentialsManager
provides a way to store the credentials, it could provide a sync method to retrieve them:Alternatives and current work-arounds
A workaround is to use directly the
A0SimpleKeychain
without relying on theAuth0.CredentialsManager
and use the samestoreKey
as the one passed in the init ofAuth0.CredentialsManager
:However, this unnecessarily exposes the
A0SimpleKeychain
as well as the way the credentials are persisted usingNSKeyedUnarchiver
. So if theAuth0.CredentialsManager
way of archiving the credentials would change, the above code would likely fail.The text was updated successfully, but these errors were encountered: