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
+4-27Lines changed: 4 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -646,43 +646,20 @@ To solve, you will want to pass in the appropriate iOS controller of the active
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
648
### getAuthToken
649
-
If you want to authenticate your user from your backend server you can obtain
650
-
a Firebase auth token for the currently logged in user.
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.
651
650
652
-
You can choose to get just the token itself or the token plus 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):
653
-
654
-
Just token:
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):
655
652
656
653
```js
657
654
firebase.getAuthToken({
658
655
// default false, not recommended to set to true by Firebase but exposed for {N} devs nonetheless :)
0 commit comments