Skip to content

Conversation

@drtechie
Copy link
Member

@drtechie drtechie commented May 23, 2025

πŸ“‹ Description

JIRA ID: AMM-1491

Fix incoming cookie name


βœ… Type of Change

  • 🐞 Bug fix (non-breaking change which resolves an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • πŸ”₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • πŸ›  Refactor (change that is neither a fix nor a new feature)
  • βš™οΈ Config change (configuration file or build script updates)
  • πŸ“š Documentation (updates to docs or readme)
  • πŸ§ͺ Tests (adding new or updating existing tests)
  • 🎨 UI/UX (changes that affect the user interface)
  • πŸš€ Performance (improves performance)
  • 🧹 Chore (miscellaneous changes that don't modify src or test files)

Summary by CodeRabbit

  • Bug Fixes
    • Adjusted the cookie name used to retrieve the JWT token, ensuring correct detection and retrieval of the authentication token from cookies.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 23, 2025

Walkthrough

The change updates the getJwtTokenFromCookie method in the IEMRAdminController class to look for a cookie named "Jwttoken" instead of "jwtToken" when retrieving the JWT token from HTTP cookies. No other logic or interface signatures are altered.

Changes

File(s) Change Summary
src/main/java/com/iemr/common/controller/users/IEMRAdminController.java Modified the cookie name comparison in getJwtTokenFromCookie to search for "Jwttoken" (case change).

Poem

A cookie’s name, so small a tweak,
From β€œjwtToken” to β€œJwttoken” we seek.
With capital J, the search is new,
The rabbit hopsβ€”precision in view!
For tokens found or lost,
We check at any cost,
And celebrate this change with code so sleek!

Note

⚑️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

✨ Finishing Touches
  • πŸ“ Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share
πŸͺ§ Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@sonarqubecloud
Copy link

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

πŸ“œ Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 10a0608 and 6263a11.

πŸ“’ Files selected for processing (1)
  • src/main/java/com/iemr/common/controller/users/IEMRAdminController.java (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: style-check / checkstyle
  • GitHub Check: Build
  • GitHub Check: Analyze (java)
  • GitHub Check: Package-test

if (cookies != null) {
for (Cookie cookie : cookies) {
if ("jwtToken".equals(cookie.getName())) {
if ("Jwttoken".equals(cookie.getName())) {
Copy link
Contributor

Choose a reason for hiding this comment

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

πŸ’‘ Verification agent

🧩 Analysis chain

Bug fix approved but inconsistency detected.

The cookie name change from "jwtToken" to "Jwttoken" appears to fix the bug as intended. However, there's an inconsistency in the same file where the getLoginResponse method (line 499) still searches for a cookie named "jwtToken".

Please verify that all cookie lookups use the correct name:


🏁 Script executed:

#!/bin/bash
# Description: Find all cookie name references to ensure consistency
# Expected: All JWT cookie references should use the same name

echo "=== Searching for JWT cookie name references ==="
rg -A 3 -B 3 'cookie\.getName\(\)' --type java

echo -e "\n=== Searching for hardcoded cookie names ==="
rg '"[Jj]wt[Tt]oken"' --type java

echo -e "\n=== Checking CookieUtil implementation ==="
ast-grep --pattern 'addJwtTokenToCookie($_, $_, $_) {
  $$$
}'

Length of output: 6798


Inconsistent JWT cookie name usage detected – fixes required

The codebase currently mixes two cookie names, "jwtToken" and "Jwttoken", for the same purpose. Since CookieUtil (and other filters) consistently use "Jwttoken", we should standardize on that value everywhere.

Please update the following:

  • IEMRAdminController.java
    • At the getLoginResponse cookie loop (line ~499):
      Change
      if ("jwtToken".equals(cookie.getName())) {
      to
      if ("Jwttoken".equals(cookie.getName())) {
  • Any other manual cookie lookups
    • Replace remaining occurrences of "jwtToken" in cookie.getName() checks with "Jwttoken".
    • Consider using CookieUtil.getCookieValue(request, COOKIE_NAME) instead of manual loops to centralize the cookie‐name constant.

Optionally, extract "Jwttoken" into a shared constant (e.g. JwtConstants.COOKIE_NAME) to prevent future typos.

πŸ€– Prompt for AI Agents
In src/main/java/com/iemr/common/controller/users/IEMRAdminController.java
around line 499 and other locations where cookie names are checked, the code
inconsistently uses "jwtToken" and "Jwttoken" for the same cookie. To fix this,
update all occurrences of cookie.getName() checks from "jwtToken" to "Jwttoken"
to match the consistent usage in CookieUtil and filters. Additionally, consider
refactoring to use a centralized constant for the cookie name, such as
JwtConstants.COOKIE_NAME, or use CookieUtil.getCookieValue(request, COOKIE_NAME)
to avoid manual loops and hardcoded strings.

@helenKaryamsetty helenKaryamsetty merged commit 8adb77f into develop May 23, 2025
7 checks passed
This was referenced May 23, 2025
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