DIAL chat version
0.0.1
How to reproduce
- Open the Toolset Editor.
- Select OAuth authentication.
- Select Custom login.
- Enter a Client ID, e.g. qa-toolset-client-8358.
- Enter a Client secret, e.g. qa-toolset-secret-8358.
- Observe the Client secret field.
- Save the toolset and reopen it in Edit mode.
- Observe the Client secret field again.
Actual result
The Client secret is displayed as plain text:
qa-toolset-secret-8358
The secret remains readable in the UI.
Before user tried to log in:
After user tried log in:
Expected result
According to the design, the Client secret must be masked and must not be displayed as plain text.
For example:
••••••••••••
The Client secret should remain masked:
- while typing;
- after pasting a value;
- after authentication/login;
- when reopening an existing toolset in Edit mode.
When editing an existing toolset, the UI should indicate that a Client secret is already configured without exposing its actual value.
If the user does not change the Client secret and saves other toolset changes, the existing secret must remain unchanged.
Confidential information
DIAL chat version
0.0.1
How to reproduce
Actual result
The Client secret is displayed as plain text:
qa-toolset-secret-8358
The secret remains readable in the UI.
Before user tried to log in:
After user tried log in:
Expected result
According to the design, the Client secret must be masked and must not be displayed as plain text.
For example:
••••••••••••
The Client secret should remain masked:
When editing an existing toolset, the UI should indicate that a Client secret is already configured without exposing its actual value.
If the user does not change the Client secret and saves other toolset changes, the existing secret must remain unchanged.
Confidential information