Skip to content

Conversation

ravishanigarapu
Copy link
Member

@ravishanigarapu ravishanigarapu commented May 28, 2025

πŸ“‹ Description

JIRA ID: AMM-1561

State district not patch because of jwttoken.


βœ… 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)

ℹ️ Additional Information

Please describe how the changes were tested, and include any relevant screenshots, logs, or other information that provides additional context.

Summary by CodeRabbit

  • New Features
    • Enhanced HTTP requests to automatically include JWT tokens in headers, improving authentication handling for all outgoing requests.

Copy link

coderabbitai bot commented May 28, 2025

Walkthrough

A new static method was added to RestTemplateUtil for extracting and injecting JWT tokens into HTTP headers. This method is now invoked in multiple HTTP methods within HttpUtils, ensuring JWT tokens are consistently added to headers before making REST calls. No changes were made to method signatures.

Changes

File(s) Change Summary
.../RestTemplateUtil.java Added getJwttokenFromHeaders(HttpHeaders headers) and extractJwttoken(HttpServletRequest) methods to handle JWT extraction and header injection.
.../http/HttpUtils.java Integrated RestTemplateUtil.getJwttokenFromHeaders(headers) calls into all HTTP method implementations to enrich headers with JWT tokens.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant HttpUtils
    participant RestTemplateUtil
    participant CookieUtil
    participant UserAgentContext

    Caller->>HttpUtils: Call HTTP method (get/post/put/uploadFile)
    HttpUtils->>RestTemplateUtil: getJwttokenFromHeaders(headers)
    RestTemplateUtil->>CookieUtil: getJwtTokenFromCookie(request)
    RestTemplateUtil->>UserAgentContext: getUserAgent()
    RestTemplateUtil-->>HttpUtils: Headers enriched with JWT token and user agent
    HttpUtils->>Caller: Proceed with HTTP request using updated headers
Loading

Possibly related PRs

Suggested reviewers

  • mo839639

Poem

A token hops from paw to paw,
Through headers now, without a flaw.
RestTemplate’s work is neat and spry,
HttpUtils gives it a try.
JWTs jump in with every callβ€”
Secure and swift, we serve them all!
πŸ‡βœ¨


πŸ“œ Recent review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 1b6d989 and b115e60.

πŸ“’ Files selected for processing (2)
  • src/main/java/com/iemr/admin/utils/RestTemplateUtil.java (2 hunks)
  • src/main/java/com/iemr/admin/utils/http/HttpUtils.java (8 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • src/main/java/com/iemr/admin/utils/http/HttpUtils.java
  • src/main/java/com/iemr/admin/utils/RestTemplateUtil.java
✨ 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.

Copy link

@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: 4

πŸ”­ Outside diff range comments (4)
src/main/java/com/iemr/admin/utils/http/HttpUtils.java (4)

111-119: ⚠️ Potential issue

Same thread safety issue as in GET method.

The shared headers instance variable creates thread safety problems.

Apply the same fix as suggested for the GET method - use local headers instead of the shared instance variable.


143-151: ⚠️ Potential issue

Same thread safety issue applies here.

The PUT method also uses the shared headers instance variable, creating the same thread safety concern.

Apply the same local headers fix as suggested for other methods.


176-215: ⚠️ Potential issue

Potential issue with uploadFile method integration.

The JWT token extraction is called inside the multipart conditional block (line 198), but not in the else block (lines 207-211). This means file uploads using non-multipart content types won't include JWT tokens.

Move the JWT token extraction outside the conditional or add it to both branches:

 	}
 	ResponseEntity<String> responseEntity = new ResponseEntity(HttpStatus.BAD_REQUEST);
+	RestTemplateUtil.getJwttokenFromHeaders(headers);
 	if (headers.getContentType().toString().equals(MediaType.MULTIPART_FORM_DATA_TYPE.toString())) {
 		HttpEntity<FormDataMultiPart> requestEntity;
 		try {
 			FormDataMultiPart multiPart = new FormDataMultiPart();
 			FileInputStream is = new FileInputStream(data);
 			FormDataBodyPart filePart = new FormDataBodyPart("content", is,
 					MediaType.APPLICATION_OCTET_STREAM_TYPE);
 			multiPart.bodyPart(filePart);
 			multiPart.field("docPath", data);
 			headers.add("Content-Type", MediaType.APPLICATION_JSON);
-			RestTemplateUtil.getJwttokenFromHeaders(headers);
 			requestEntity = new HttpEntity<FormDataMultiPart>(multiPart, headers);

80-198: πŸ› οΈ Refactor suggestion

Consider error handling for RequestContext unavailability.

All method calls to RestTemplateUtil.getJwttokenFromHeaders() could potentially fail if called outside a web request context (e.g., in background threads). Consider adding error handling or documentation about this limitation.

Add error handling around the JWT token extraction calls:

 try {
 	RestTemplateUtil.getJwttokenFromHeaders(headers);
 } catch (Exception e) {
 	logger.warn("Unable to extract JWT token from request context: " + e.getMessage());
 	// Continue with request without JWT token
 }

Would you like me to generate a comprehensive refactoring that addresses the thread safety issues and adds proper error handling across all methods?

🧹 Nitpick comments (1)
src/main/java/com/iemr/admin/utils/RestTemplateUtil.java (1)

52-52: Fix method naming convention.

The method name should follow Java naming conventions. "JWT" should be capitalized as "Jwt" rather than "Jwttoken".

-public static void getJwttokenFromHeaders(HttpHeaders headers) {
+public static void getJwtTokenFromHeaders(HttpHeaders headers) {
πŸ“œ Review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 0e2e9a6 and 1b6d989.

πŸ“’ Files selected for processing (2)
  • src/main/java/com/iemr/admin/utils/RestTemplateUtil.java (1 hunks)
  • src/main/java/com/iemr/admin/utils/http/HttpUtils.java (8 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (2)
src/main/java/com/iemr/admin/utils/RestTemplateUtil.java (2)
src/main/java/com/iemr/admin/utils/UserAgentContext.java (1)
  • UserAgentContext (3-18)
src/main/java/com/iemr/admin/utils/Constants.java (1)
  • Constants (3-9)
src/main/java/com/iemr/admin/utils/http/HttpUtils.java (1)
src/main/java/com/iemr/admin/utils/RestTemplateUtil.java (1)
  • RestTemplateUtil (15-75)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (java)
πŸ”‡ Additional comments (4)
src/main/java/com/iemr/admin/utils/http/HttpUtils.java (4)

40-40: LGTM! Import statement added correctly.

The import for RestTemplateUtil is properly added and necessary for the new functionality.


92-109: LGTM! Consistent integration pattern.

The JWT token extraction is properly integrated into the GET method with custom headers. The placement after header setup but before request execution is correct.


121-142: LGTM! Proper integration with custom headers.

The JWT token extraction is correctly integrated after custom headers are set up but before the request is executed.


153-174: LGTM! Consistent with other parameterized methods.

The integration follows the same correct pattern as other methods that accept custom headers.

Comment on lines 57 to 73
String jwtTokenFromCookie = null;
try {
jwtTokenFromCookie = CookieUtil.getJwtTokenFromCookie(requestHeader);

} catch (Exception e) {
logger.error("Error while getting jwtToken from Cookie" + e.getMessage());
}
if (null != UserAgentContext.getUserAgent()) {
headers.add(HttpHeaders.USER_AGENT, UserAgentContext.getUserAgent());
}
if (null != jwtTokenFromCookie) {
headers.add(Constants.JWT_TOKEN, jwtTokenFromCookie);
} else if (null != requestHeader.getHeader(Constants.JWT_TOKEN)) {
headers.add(Constants.JWT_TOKEN, requestHeader.getHeader(Constants.JWT_TOKEN));
}

}
Copy link

Choose a reason for hiding this comment

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

πŸ› οΈ Refactor suggestion

Consider refactoring to eliminate code duplication.

This method contains nearly identical logic to the existing createRequestEntity method (lines 28-47). The JWT token extraction, User-Agent handling, and header manipulation logic is duplicated.

Consider extracting the common JWT token logic into a separate private method:

+private static String extractJwtToken(HttpServletRequest request) {
+	try {
+		return CookieUtil.getJwtTokenFromCookie(request);
+	} catch (Exception e) {
+		logger.error("Error while getting jwtToken from Cookie" + e.getMessage());
+		return null;
+	}
+}
+
+private static void enrichHeadersWithTokenAndUserAgent(HttpHeaders headers, HttpServletRequest request) {
+	String jwtTokenFromCookie = extractJwtToken(request);
+	
+	if (null != UserAgentContext.getUserAgent()) {
+		headers.add(HttpHeaders.USER_AGENT, UserAgentContext.getUserAgent());
+	}
+	if (null != jwtTokenFromCookie) {
+		headers.add(Constants.JWT_TOKEN, jwtTokenFromCookie);
+	} else if (null != request.getHeader(Constants.JWT_TOKEN)) {
+		headers.add(Constants.JWT_TOKEN, request.getHeader(Constants.JWT_TOKEN));
+	}
+}

Then update both methods to use this shared logic.

Committable suggestion skipped: line range outside the PR's diff.

πŸ€– Prompt for AI Agents
In src/main/java/com/iemr/admin/utils/RestTemplateUtil.java around lines 28 to
73, the JWT token extraction, User-Agent handling, and header manipulation logic
is duplicated between the current method and createRequestEntity. Refactor by
extracting the common JWT token retrieval and header setup logic into a private
helper method. Then update both methods to call this helper to avoid code
duplication and improve maintainability.

Copy link

@ravishanigarapu ravishanigarapu merged commit 5485662 into PSMRI:develop May 28, 2025
7 checks passed
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.

2 participants