-
Notifications
You must be signed in to change notification settings - Fork 8
[SCAL-288254] Token Refresh #393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Summary of ChangesHello @ruchI9897, 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 introduces a robust token refresh mechanism to enhance the user experience in embedded applications. By proactively fetching new authentication tokens when existing ones are nearing expiry, it ensures continuous authentication for cookieless trusted authentication scenarios, thereby preventing session timeouts and maintaining an uninterrupted user session. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a mechanism for refreshing authentication tokens, primarily for cookieless authentication. The changes include adding a getFreshToken parameter to getAuthenticationToken, defining a new RefreshAuthToken embed event, and implementing the tokenRefresh handler to fetch and provide a new token when requested.
My review focuses on improving the maintainability of the new tokenRefresh method. I've suggested adding proper types to its parameters to enhance type safety and pointed out code duplication with the existing updateAuthToken method, recommending a refactor to a shared helper function. These changes will make the code cleaner and easier to maintain.
| * @param _ | ||
| * @param responder | ||
| */ | ||
| private tokenRefresh = async (_: any, responder: any) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For better type safety and code clarity, consider providing specific types for the _ and responder parameters instead of any. Based on the on method signature, _ can be typed as MessagePayload and responder as (data: any) => void. You'll need to import MessagePayload from ../types.
| private tokenRefresh = async (_: any, responder: any) => { | |
| private tokenRefresh = async (_: MessagePayload, responder: (data: any) => void) => { |
| try { | ||
| const authToken = await getAuthenticationToken(this.embedConfig, true); | ||
| responder({ | ||
| type: EmbedEvent.RefreshAuthToken, | ||
| data: { authToken }, | ||
| }); | ||
| } catch (e) { | ||
| logger.error(`${ERROR_MESSAGE.INVALID_TOKEN_ERROR} Error : ${e?.message}`); | ||
| processAuthFailure(e, this.isPreRendered ? this.preRenderWrapper : this.el); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This try...catch block is nearly identical to the one in the updateAuthToken method (lines 544-553). To improve code maintainability and adhere to the DRY (Don't Repeat Yourself) principle, consider extracting this logic into a shared private helper method. This helper could take parameters for getFreshToken and the EmbedEvent type to handle the minor differences between the two usages.
commit: |
|
SonarQube Quality Gate
|








No description provided.