Maintain persistence for firebaseToken in AuthImpl object #9119
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Implement InitializeAuth changes for BYO-CIAM Firebase Auth * Removing white space * Addressing review comments * Adding Unit test for initializeAuth with TenantConfig dependency * Running yarn run demo * Update doc
* Throw not supported exception in _performApiRequest
* Throw Operation Not Allowed for Invalid Auth Endpoint (#9013) (#9019) * Throw Operation Not Allowed for Invalid Auth Endpoint (#9013) (#9019) * Implement exchangeToken public api * Using expiry_in returned by backend * Addressing review comments and adding some Unit test * Docgen * Addressing review comments and adding some Unit test * Typo * yarn docgen * Fixing typo * yarn run format
* Write Firebase Token to Auth instance * yarn run format * Fix unit test and run yarn docgen:all * Address comments
* Write Firebase Token to Auth instance * yarn run format * Fix unit test and run yarn docgen:all * getFirebaseToken Auth Interop method for BYO-CIAM * Add unit test * Adding Unit test * Running yarn docgen:all * Use getToken instead of getFirebaseToken * Adding Unit test * yarn run format * Remove unused method
mansisampat
requested review from
a team,
NhienLam,
Xiaoshouzi-gh,
lisajian,
pashanka and
sam-gc
as code owners
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected Products
Test Logs |
pashanka
reviewed
Jun 25, 2025
| if (firebaseToken) { | ||
| await this.assertedPersistence.setFirebaseToken(firebaseToken); | ||
| } else { | ||
| await this.assertedPersistence.removeFirebaseToken(); |
There was a problem hiding this comment.
You will have to do same for signOut as well right?
There was a problem hiding this comment.
Correct. I plan to create a separate CL for signOut logic. Please let me know if you see any concerns.
NhienLam
reviewed
Jun 30, 2025
| onAbort?: () => void | ||
| ): Unsubscribe; | ||
|
|
||
| onFirebaseTokenChanged( |
There was a problem hiding this comment.
q: When do we call onFirebaseTokenChanged?
- Please add jsdoc
- Do we need to implement a onFirebaseTokenChanged function in packages/auth/src/core/index.ts ?
There was a problem hiding this comment.
Hey, I onFirebaseTokenChanged is a callback method that is triggered when firebase token is updated i.e. during the following scenarios -
- On App initialization when FirebaseToken is fetched from the persistence.
- When a getToken method is triggered and the token is expired. In this case the firebaseToken is updated to
null.
The callback method was initially not planned. I had a discussion with pavanshankar@ and we decided on decoupling the persistence logic with the callback method.
Created a PR - #9138 for persisting the firebaseToken for BYO-CIAM.
sam-gc
reviewed
Jun 30, 2025
| onAbort?: () => void | ||
| ): Unsubscribe; | ||
|
|
||
| onFirebaseTokenChanged( |
There was a problem hiding this comment.
Related: this method was not part of the API review. I'm concerned that onFirebaseTokenChanged (and the concept of a FirebaseToken) is very generic sounding. I'm worried it'll confuse users.
There was a problem hiding this comment.
Agreed.
The onFirebaseTokenChanged callback method was initially not planned during the API Review. Had a discussion with pavanshankar@ offline. Currently decoupling the callback from the persistence changes.
Created a PR - #9138 for persisting the firebaseToken for BYO-CIAM.
There was a problem hiding this comment.
We should go through another API review process surfacing this. "firebaseToken" is a really generic name -- "Firebase" is a huge suite of products that has many different types of tokens. Any and every change to the public API surface needs to go through review
mansisampat
force-pushed
the
gcip-byociam-web
branch
2 times, most recently
from
b18b769 to
ac2fc52
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there! So you want to contribute to a Firebase SDK?
Before you file this pull request, please read these guidelines:
Discussion
Testing