Skip to content

Conversation

@DivyaPremanantha
Copy link
Contributor

@DivyaPremanantha DivyaPremanantha commented Nov 20, 2025

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email [email protected] to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to [email protected] and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

  • Unit tests

    Code coverage information

  • Integration tests

    Details about the test cases and coverage

Security checks

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

Summary by CodeRabbit

  • Documentation
    • Fixed image asset paths and enhanced image rendering consistency in the Mutual TLS authentication guide.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Nov 20, 2025

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • en/docs/assets/img/authentication-and-authorization/mutual-ssl-authentication.png is excluded by !**/*.png

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A single documentation file received updates correcting relative image asset paths from ../assets/ to ../../assets/ and adding inline width styling attributes to image embeds. Minor text formatting adjustments accompanied these changes.

Changes

Cohort / File(s) Summary
Documentation updates
en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md
Corrected relative image asset paths (from ../assets/ to ../../assets/); added inline width styling to multiple image embeds (300px, 500px); applied minor text formatting adjustments.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Simple, repetitive path corrections across a single documentation file
  • Styling additions follow a consistent pattern
  • No logic or functional changes to evaluate

Poem

🐰 A path through the meadow, now clearly defined,
With images sized just to suit every mind,
Two dots lead the way where the assets reside,
No tunnel of confusion, just clarity's guide!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description contains only the template structure with placeholder text and no actual implementation details or answers to any required sections. Fill in the template sections with relevant details such as the purpose of the fix, the specific problems addressed, and justification for why this change was needed.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: fixing image loading issues in the MTLS documentation by updating relative paths and adding inline styles.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

Comment @coderabbitai help to get the list of available commands and usage tips.

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: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 71accff and 5651ae3.

📒 Files selected for processing (1)
  • en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md (4 hunks)
🔇 Additional comments (1)
en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md (1)

49-49: Inline style attributes are consistently applied with appropriate widths.

All image embeds now include explicit width constraints using valid Kramdown syntax {: style="width:XXXpx"}. The width distribution is sensible: 300px for dialog/compact UI elements (lines 49, 77) and 500px for larger detailed views (lines 55, 59, 83, 87, 100). This ensures predictable rendering across different screen sizes.

Also applies to: 55-55, 59-59, 77-77, 83-83, 87-87, 100-100

Mutual TLS authentication involves both the client and server validating each other’s certificates before establishing a connection. The following diagram depicts this scenario:

![Mutual TLS authentication](../assets/img/authentication-and-authorization/mutual-ssl-authentication.png)
![Mutual TLS authentication](../../assets/img/authentication-and-authorization/mutual-ssl-authentication.png)
Copy link

@coderabbitai coderabbitai bot Nov 20, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

Verify the corrected relative path is accurate.

The asset path was updated from ../assets/ to ../../assets/. Given the file's depth at en/docs/develop-api-proxy/authentication-and-authorization/, verify that ../../assets/ correctly resolves to the project's image assets directory.


🏁 Script executed:

#!/bin/bash
# Description: Verify the asset path structure and confirm the corrected path resolves correctly.

# Check if assets directory exists at the expected location
fd -t d "^assets$" en/docs/ --max-depth 1

# List sample image files from the target directory to confirm accessibility
fd "mutual-ssl-authentication" en/docs/

# Show the directory structure around the assets folder
tree -L 2 en/docs/ 2>/dev/null || find en/docs/ -maxdepth 2 -type d | head -20

Length of output: 1822


I need to inspect the complete file to verify all the changes mentioned in the review comment, particularly the inline style additions and text anomalies.


---

🏁 Script executed:

```shell
#!/bin/bash
# Retrieve the full file to verify all changes
cat en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md

Length of output: 8426


Fix double-space typo on line 85.

The relative path correction to ../../assets/ is correct and resolves to the proper image directory. The Kramdown inline style syntax is valid. However, line 85 contains a formatting error: "This opens the certificate" has an extra space between "the" and "certificate"—should be "This opens the certificate".

🤖 Prompt for AI Agents
en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md
line 85: remove the extra space between "the" and "certificate" so the sentence
reads "This opens the certificate" (update the markdown file to correct the
typo).

Copy link
Contributor

Choose a reason for hiding this comment

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

Is it possible to remove the term Choreo Gateway here and have Gateway or Bijira Gateway?

Copy link

Choose a reason for hiding this comment

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for "Choreo Gateway" in the repository
echo "=== Searching for 'Choreo Gateway' occurrences ==="
rg -n "Choreo Gateway" --type=md

echo -e "\n=== Searching for 'Choreo' (case-sensitive) ==="
rg -n "\bChoreo\b" --type=md

Length of output: 2057


@pubudu538 Based on my search of the repository, there are no occurrences of "Choreo Gateway" in the codebase. The file under review (secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md) already consistently uses "Bijira Gateway" throughout the document.

I did find some references to "Choreo" in other contexts across the documentation:

  • References to WSO2 Choreo as a product/platform
  • Role names like "Choreo Platform Engineer" and "Choreo DevOps"
  • "Choreo Developer Portal" in some files

However, none of these are using "Choreo Gateway" - they're all using "Bijira Gateway" where gateway terminology is needed.

Is there a specific instance of "Choreo Gateway" you'd like me to locate and update? Or are you looking to establish this as a general documentation standard? If you can point me to a specific file or location, I can help update it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated the image

Copy link

Choose a reason for hiding this comment

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

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

![View and download certificate](../../assets/img/authentication-and-authorization/view-and-download.png){: style="width:500px"}
This opens the certificate for you to view and download.
This opens the certificate for you to view and download.
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

Minor text formatting anomaly.

Line 85 contains "the certificate" with an extra space. Confirm whether this is intentional or an unintended artifact from the editing process.


🏁 Script executed:

#!/bin/bash
# Description: Check for double spaces and other formatting anomalies in the updated file.

# Search for double spaces in the file
grep -n "  " "en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md" | head -10

Length of output: 1332


I need to verify the exact content at line 85 to confirm the double space issue.


---

🏁 Script executed:

```shell
#!/bin/bash
# Display line 85 specifically
sed -n '85p' "en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md"

Length of output: 64


Fix double space in line 85.

Line 85 contains "the certificate" with an extra space. Update to "the certificate".

🤖 Prompt for AI Agents
In
en/docs/develop-api-proxy/authentication-and-authorization/secure-communication-between-the-bijira-gateway-and-your-backend-with-mutual-tls.md
around line 85, there is a double space in the phrase "the  certificate"; edit
that line to remove the extra space so it reads "the certificate" (i.e., replace
the two spaces with a single space).

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