Skip to content

Conversation

@Divyansh-db
Copy link
Contributor

@Divyansh-db Divyansh-db commented Oct 17, 2025

What changes are proposed in this pull request?

We recently added support for disabling auto token refresh (#525). The current code is hardcoded to handle refreshable tokens, and it forcefully refreshes the token on every call of configure()
This PR proposed using a token (no matter if it is refreshable or not) if it is valid. Once the ExternalBrowserCredentialsProvider is run, it stores the token on disk. If the application is run again, it checks the token and tries to use it.

How is this tested?

Added Unit tests

NO_CHANGELOG=true

Copy link
Contributor

@renaudhartert-db renaudhartert-db left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM modulo fix to the changelogs.

Note: unit tests are great but it would also be good to validate that the code works locally.

@github-actions
Copy link

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/sdk-java

Inputs:

  • PR number: 526
  • Commit SHA: 3418f402039e8c82c70f7c32dc5d18f96d0a9397

Checks will be approved automatically on success.

@Divyansh-db
Copy link
Contributor Author

Checked the code locally. Browser Authentication is not triggered again (for refreshable and non-refreshable) if the token file already exists.

@Divyansh-db Divyansh-db added this pull request to the merge queue Oct 22, 2025
Merged via the queue into main with commit 54b94b1 Oct 22, 2025
16 of 17 checks passed
@Divyansh-db Divyansh-db deleted the divyansh-vijayvergia_data/fix_external_browser_cred_provider branch October 22, 2025 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants