Replies: 1 comment 1 reply
-
Hello, So yes, you can still get an access token. 👍 Hope this helps! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I’m currently using the Original Sign-in (free) and am considering paying for the Universal Sign-In (premium), primarily for the Android Credential Manager support as it is a requirement in 2025.
At the moment, my implementation relies on the access token retrieved via the
getTokens
method. However, after reviewing the migration table, I noticed that the recommended approach involves using thesignIn
orrequestAuthorization
methods instead. It’s not clear, though, whether an access token will still be returned when using these methods.I understand that the ideal approach is to use an
idToken
rather than anaccessToken
, as using an access token for identity assertion on a backend server is discouraged.Could you clarify whether switching to the Universal Sign-In (premium) version would require me to update my backend to expect an
idToken
(as outlined here), or if I could complete the frontend migration without needing to modify my backend?Beta Was this translation helpful? Give feedback.
All reactions