Skip to content

Conversation

@drtechie
Copy link
Member

@drtechie drtechie commented May 23, 2025

πŸ“‹ Description

JIRA ID: AMM-1456

Ensure cookie is correctly checked in login response API


βœ… 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
    • Improved cookie handling to recognize the JWT token regardless of capitalization, ensuring smoother login experiences when the token is stored with different case variations.

@drtechie drtechie requested a review from ravishanigarapu May 23, 2025 13:06
@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 23, 2025

Walkthrough

The change updates the logic in the getLoginResponse method of IEMRAdminController to perform a case-insensitive comparison when checking for the JWT token cookie, switching from a strict "jwtToken" match to using equalsIgnoreCase("Jwttoken"). No other functionality or method signatures are altered.

Changes

File(s) Change Summary
src/main/java/com/iemr/common/controller/users/IEMRAdminController.java Modified cookie name comparison in getLoginResponse to use case-insensitive matching for "Jwttoken".

Possibly related PRs

Suggested reviewers

  • ravishanigarapu

Poem

A cookie’s name, once strict and bold,
Now greets all cases, young and old.
Whether β€œjwtToken” or β€œJwttoken” you bring,
The login will workβ€”let the user in!
Little tweaks, big relief,
Code hops forward, oh what a feat! πŸ‡

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

Quality Gate Failed Quality Gate failed

Failed conditions
D Maintainability Rating on New Code (required β‰₯ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@drtechie drtechie merged commit 0cc609d into develop May 23, 2025
5 of 6 checks passed
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

🧹 Nitpick comments (1)
src/main/java/com/iemr/common/controller/users/IEMRAdminController.java (1)

495-505: Consider extracting duplicated cookie lookup logic.

This cookie lookup logic is duplicated in the getJwtTokenFromCookie method (lines 1093-1101). Consider extracting this into a helper method to follow DRY principles.

+private String extractJwtTokenFromCookies(Cookie[] cookies) {
+    if (cookies != null) {
+        for (Cookie cookie : cookies) {
+            if ("Jwttoken".equalsIgnoreCase(cookie.getName())) {
+                return cookie.getValue();
+            }
+        }
+    }
+    return null;
+}

Then use it in both methods:

-                if (jwtToken == null) {
-                    Cookie[] cookies = request.getCookies();
-                    if (cookies != null) {
-                        for (Cookie cookie : cookies) {
-                            if ("Jwttoken".equalsIgnoreCase(cookie.getName())) {
-                                jwtToken = cookie.getValue();
-                                break;
-                            }
-                        }
-                    }
-                }
+                if (jwtToken == null) {
+                    jwtToken = extractJwtTokenFromCookies(request.getCookies());
+                }
πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 05446fd and dadb5d0.

πŸ“’ 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: Analyze (java)
  • GitHub Check: Package-test
  • GitHub Check: Build

if (cookies != null) {
for (Cookie cookie : cookies) {
if ("jwtToken".equals(cookie.getName())) {
if ("Jwttoken".equalsIgnoreCase(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

Good fix for case-sensitivity, but verify cookie name consistency.

The change to use equalsIgnoreCase() is a good practice for robust cookie handling. However, please ensure that the cookie name "Jwttoken" exactly matches how the cookie is set elsewhere in the application.

Let me verify the cookie naming consistency across the codebase:


🏁 Script executed:

#!/bin/bash
# Description: Check for JWT cookie naming patterns to ensure consistency

# Search for cookie setting operations
echo "=== Cookie Setting Operations ==="
rg -A 3 -B 3 "addJwtTokenToCookie|setCookie|addCookie" --type java

# Search for JWT token cookie references
echo "=== JWT Token Cookie References ==="
rg -A 2 -B 2 "jwtToken|Jwttoken|JWT.*[Cc]ookie" --type java

# Search in CookieUtil to see how the cookie is actually named
echo "=== CookieUtil Implementation ==="
fd "CookieUtil" --type f --extension java --exec cat {}

Length of output: 17692


Approve case‐insensitive cookie comparison; cookie name is consistent.

All JWT cookies are consistently named "Jwttoken" when set and read. To eliminate duplicated lookup logic, please refactor the manual loops to use the existing utility method:

β€’ src/main/java/com/iemr/common/controller/users/IEMRAdminController.java
– Line 499 in getLoginResponse (manual cookie loop)
– getJwtTokenFromCookie endpoint (around line 1095)
β€’ src/main/java/com/iemr/common/utils/JwtUserIdValidationFilter.java
– Cookie lookup block using equalsIgnoreCase("Jwttoken")

Replace each manual loop with a call to CookieUtil.getJwtTokenFromCookie(request) for better DRY and consistency.

πŸ€– Prompt for AI Agents
In src/main/java/com/iemr/common/controller/users/IEMRAdminController.java at
line 499, the manual loop checking for the "Jwttoken" cookie using
equalsIgnoreCase should be refactored to use the existing utility method
CookieUtil.getJwtTokenFromCookie(request). This change will remove duplicated
cookie lookup logic, improve code consistency, and adhere to DRY principles.
Locate all manual cookie loops for JWT token retrieval in this file and in
JwtUserIdValidationFilter.java and replace them with calls to
CookieUtil.getJwtTokenFromCookie(request).

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