Done
Details
Assignee
Dmytro MelnyshynDmytro MelnyshynReporter
Brooks TravisBrooks TravisPriority
P2Story Points
1Sprint
NoneDevelopment Team
VolarisFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Dmytro Melnyshyn
Dmytro MelnyshynReporter
Brooks Travis
Brooks TravisPriority
Story Points
1
Sprint
None
Development Team
Volaris
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 3, 2021 at 12:14 PM
Updated September 17, 2021 at 11:20 AM
Resolved September 13, 2021 at 2:18 PM
Purpose:
User story statement(s):
As a FOLIO user with permission to modify INN-Reach central server configurations,
I want the "secret" in the central and local server key pairs to be obfuscated once saved
so that they are not readily visible to someone "looking over my shoulder" (or, perhaps, watching a live or recorded demo of functionality.
Note: The backend response does not need to obfuscate the content, just the front-end.
Scenarios:
Scenario:
Given a central server configuration has been created and saved
When when the user enters the "edit" mode
Then any values saved in the central server secret field should be obfuscated (eg. treated as a password field)
Scenario:
Given a central server configuration has been created and saved
When when the user enters the "edit" mode
Then any values saved in the local server secret field should be obfuscated (eg. treated as a password field)
Extra: If not too much additional work, the ability to show/hide the field on demand (default to hidden) would be nice.