feat: ability to update credentials on long running client#4371
feat: ability to update credentials on long running client#4371
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the Spanner client library by providing a mechanism to update authentication credentials dynamically within a running application. This is particularly beneficial for long-lived services that need to refresh or change their service account credentials without incurring downtime or complex client re-initialization logic, thereby improving security posture and operational flexibility. Highlights
Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a "MutableCredentials" class to enable dynamic updating of service account credentials for long-running Spanner clients, facilitating credential rotation without client re-initialization. However, the current implementation has thread-safety issues and exposes mutable internal state, which could lead to security vulnerabilities in a multi-threaded environment. Specifically, the lack of "volatile" on the "delegate" field and the exposure of the mutable "scopes" list need to be addressed. While the overall structure is good and includes tests, these security concerns are critical.
google-cloud-spanner/src/main/java/com/google/cloud/spanner/connection/MutableCredentials.java
Outdated
Show resolved
Hide resolved
google-cloud-spanner/src/main/java/com/google/cloud/spanner/connection/MutableCredentials.java
Outdated
Show resolved
Hide resolved
google-cloud-spanner/src/main/java/com/google/cloud/spanner/connection/MutableCredentials.java
Show resolved
Hide resolved
...d-spanner/src/test/java/com/google/cloud/spanner/connection/it/ITMutableCredentialsTest.java
Show resolved
Hide resolved
...-cloud-spanner/src/test/java/com/google/cloud/spanner/connection/MutableCredentialsTest.java
Show resolved
Hide resolved
…nnection/MutableCredentials.java Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
This feature introduces the ability to change Service Account credentials on a long running client without having to restart the client.
Usage: