Skip to content

Swagger Changes - #67

Merged
helenKaryamsetty merged 1 commit into
PSMRI:developfrom
ravishanigarapu:develop
Apr 3, 2025
Merged

Swagger Changes#67
helenKaryamsetty merged 1 commit into
PSMRI:developfrom
ravishanigarapu:develop

Conversation

@ravishanigarapu

@ravishanigarapu ravishanigarapu commented Apr 1, 2025

Copy link
Copy Markdown
Contributor

📋 Description

JIRA ID:

Please provide a summary of the change and the motivation behind it. Include relevant context and details.


✅ 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 API documentation access by allowing these pages to load without requiring authentication.
    • Expanded handling for static resources ensures improved delivery of UI assets and restoration of version information, contributing to a smoother experience.

@coderabbitai

coderabbitai Bot commented Apr 1, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

This pull request updates two components. In the JWT user ID validation filter, additional conditions are added so that requests starting with /swagger-ui and /v3/api-docs bypass JWT validation, with logging remaining unchanged. In the HTTP request interceptor, several new cases are introduced to handle static resource endpoints (e.g., index.html, index.css, Swagger-related scripts and styles, favicons), and the previously removed version case is restored. No public entity declarations were modified.

Changes

File Path(s) Change Summary
src/main/java/com/wipro/fhir/utils/JwtUserIdValidationFilter.java Added conditions in the skip logic for requests starting with /swagger-ui and /v3/api-docs, preserving existing flow and logging.
src/main/java/com/wipro/fhir/utils/http/HTTPRequestInterceptor.java Introduced new switch cases for endpoints (index.html, index.css, swagger-initializer.js, swagger-config, swagger-ui-bundle.js, swagger-ui.css, swagger-ui-standalone-preset.js, favicon-32x32.png, favicon-16x16.png) and restored the version case, leaving standard processing unaffected.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant JWTFilter
    Client->>JWTFilter: Send HTTP request (e.g., /swagger-ui)
    JWTFilter->>JWTFilter: Evaluate request path conditions
    alt Path matches (/swagger-ui, /v3/api-docs)
        JWTFilter->>JWTFilter: Log skip event and bypass validation
    else
        JWTFilter->>JWTFilter: Perform standard JWT user ID validation
    end
    JWTFilter->>Client: Return processing result
Loading
sequenceDiagram
    participant Client
    participant Interceptor
    Client->>Interceptor: Send HTTP request (e.g., index.html)
    Interceptor->>Interceptor: Evaluate URI in switch block
    alt URI matches new static asset cases
        Interceptor->>Client: Bypass further processing (execute break)
    else
        Interceptor->>Interceptor: Execute standard validation for request
    end
    Interceptor->>Client: Return response
Loading

Poem

I hop through code with joyful glee,
Skipping validation like leaves set free.
Swagger paths and endpoints bold,
In each new case, a story told.
I celebrate each change I see—
A rabbit's dance in tech's spree! 🐇✨

✨ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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

sonarqubecloud Bot commented Apr 1, 2025

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/main/java/com/wipro/fhir/utils/http/HTTPRequestInterceptor.java (1)

72-82: Added Swagger UI resource paths correctly

The addition of case statements for Swagger UI static resources is appropriate and consistent with the JWT filter changes. This ensures that all necessary Swagger UI components can be accessed without authentication.

Consider refactoring this growing switch statement to use a collection of excluded paths for better maintainability:

-				switch (requestAPI) {
-
-				// case "patient":
-				case "swagger-ui.html":
-				case "index.html":
-				case "index.css":
-				case "swagger-initializer.js":
-				case "swagger-config":
-				case "swagger-ui-bundle.js":
-				case "swagger-ui.css":
-				case "ui":
-				case "swagger-ui-standalone-preset.js":
-				case "favicon-32x32.png":
-				case "favicon-16x16.png":
-				case "swagger-resources":
-				case "api-docs":
-				case "version":
-
-					break;
+				// Define a set of paths that should bypass validation
+				Set<String> bypassPaths = new HashSet<>(Arrays.asList(
+					"swagger-ui.html", "index.html", "index.css", 
+					"swagger-initializer.js", "swagger-config", 
+					"swagger-ui-bundle.js", "swagger-ui.css", "ui",
+					"swagger-ui-standalone-preset.js", 
+					"favicon-32x32.png", "favicon-16x16.png",
+					"swagger-resources", "api-docs", "version"
+					// Add future paths here without modifying the switch statement
+				));
+				
+				if (bypassPaths.contains(requestAPI)) {
+					break;
+				}
+				
+				switch (requestAPI) {

Also applies to: 84-84

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 244d8a4 and 9145ccf.

📒 Files selected for processing (2)
  • src/main/java/com/wipro/fhir/utils/JwtUserIdValidationFilter.java (1 hunks)
  • src/main/java/com/wipro/fhir/utils/http/HTTPRequestInterceptor.java (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
src/main/java/com/wipro/fhir/utils/JwtUserIdValidationFilter.java (2)
Learnt from: indraniBan
PR: PSMRI/FHIR-API#53
File: src/main/java/com/wipro/fhir/utils/JwtUserIdValidationFilter.java:67-68
Timestamp: 2025-04-01T14:21:29.288Z
Learning: In security-related components like JWT filters, avoid logging sensitive information like tokens. Instead, log boolean indicators or events/outcomes for debugging purposes.
Learnt from: indraniBan
PR: PSMRI/FHIR-API#53
File: src/main/java/com/wipro/fhir/utils/JwtUserIdValidationFilter.java:53-54
Timestamp: 2025-04-01T14:21:29.289Z
Learning: In the FHIR-API project, logging JWT token processing (without the actual token value) is acceptable and required for analysis purposes.
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (java)
🔇 Additional comments (1)
src/main/java/com/wipro/fhir/utils/JwtUserIdValidationFilter.java (1)

58-59: Appropriate exclusion of Swagger endpoints from JWT validation

The addition of conditions to bypass JWT validation for Swagger UI and OpenAPI specification endpoints is appropriate. This change ensures that API documentation is publicly accessible without authentication, which is a standard practice for developer-friendly APIs.

@helenKaryamsetty
helenKaryamsetty merged commit 38cbe6b into PSMRI:develop Apr 3, 2025
@coderabbitai coderabbitai Bot mentioned this pull request May 22, 2025
10 tasks
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