-
Notifications
You must be signed in to change notification settings - Fork 359
Open
Labels
enhancementNew feature or requestNew feature or requesttriageIssues / Features awaiting triageIssues / Features awaiting triage
Description
🧭 Type of Feature
Please select the most appropriate category:
- Enhancement to existing functionality
🧭 Epic
Title: Add a toggle to mask/unmask inputs on password/sensitive info textboxes.
Goal: When admins configure/edit MCP servers and adds/updates an authentication type (Basic, Bearer Token or Custom Headers), they get to verify if the sensitive data like basic auth password, bearer token and custom header values that they set are correct or not by toggling of masking.
Why now: Admins benefit by knowing for sure that the values they configured are correct.
🙋♂️ User Story 1
As a: Admin
I want: To be able to view the sensitive info like basic auth password, bearer token and custom headers that I configured
So that: I can verify that I have entered the correct values
✅ Acceptance Criteria
Scenario: Masking/Unmasking toggle works when configuring Basic Auth
Given an admin configures Basic Auth authentication
And inputs the password
When the admin clicks on the mask-toggle button on the textbox
Then the textbox should mask/unmask the input value based on the toggle state
Scenario: Masking/Unmasking toggle works when configuring Bearer Token
Given an admin configures Bearer Token authentication
And inputs the Bearer Token
When the admin clicks on the mask-toggle button on the textbox
Then the textbox should mask/unmask the input value based on the toggle state
Scenario: Masking/Unmasking toggle works when configuring Custom Headers
Given an admin configures Custom Headers based authentication
And inputs the one or more custom headers
When the admin clicks on the mask-toggle button on the textboxes for the custom headers
Then the textboxes should mask/unmask the input value based on the toggle state🔗 MCP Standards Check
- Change adheres to current MCP specifications
- No breaking changes to existing MCP-compliant integrations
- If deviations exist, please describe them below:

Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requesttriageIssues / Features awaiting triageIssues / Features awaiting triage