You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 4, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: docs/AUTHENTICATION.md
+17-2Lines changed: 17 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -645,11 +645,15 @@ To solve, you will want to pass in the appropriate iOS controller of the active
645
645
2. Google Sign-In requires an SHA1 fingerprint: see [Authenticating Your Client for details](https://developers.google.com/android/guides/client-auth). If you don't do this you will see the account selection popup, but you won't be able to actually sign in.
646
646
3. Those fingerprints need to be added to your Firebase console. Go to 'project overview', 'project settings', then scroll down a bit.
647
647
648
-
### getAuthToken
648
+
### getAuthToken / getIdToken
649
649
If you want to authenticate your user from your backend server you can obtain a Firebase auth token for the currently logged in user.
650
650
651
651
You'll get the token, as well as the provider that was used to sign in, and any custom claims you may have previously set via the Firebase Admin SDK as outlined [here](https://firebase.google.com/docs/auth/admin/custom-claims):
652
652
653
+
654
+
<details>
655
+
<summary>Native API</summary>
656
+
653
657
```js
654
658
firebase.getAuthToken({
655
659
// default false, not recommended to set to true by Firebase but exposed for {N} devs nonetheless :)
@@ -666,6 +670,17 @@ You'll get the token, as well as the provider that was used to sign in, and any
0 commit comments