Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 114
-
3
-
Spitfire
Description
Background
In order to configure APIGEE client id and secret key, deployment teams will have to configure it by making an INSERT query to DB. Make that configurable from the UI instead as part of UC settings.
Requirements
- A tenant can configure the same client ID and API key credentials for multiple libraries
- The secret should not be visible to the end-user and can be replaced with *** when the UI tries to GET it. However, they should be able to update it.
Location
Settings > eholdings > Usage Consolidation
Two new fields:
1 - Usage consolidation client ID
– required field
– user enters string but display encrypted
2 - Usage consolidation API key
– required field
– user enters string but display encrypted
Acceptance Criteria
Given user enters client id and secret key and Usage Consolidation ID value
When s/he hits Save
AND all credentials are valid
Then update the record with these values
Given user enters client id and secret key and Usage Consolidation ID value
When s/he hits Save
AND one of the credentials is not valid
Then do not save the update
AND return a message [Usage Consolidation credentials are not valid.]
Given user enters client id and secret key and Usage Consolidation ID value
When s/he hits Save
AND the request is not successful BUT not due to user entering bad credentials
Then do not save the update
AND return a message [Usage Consolidation credentials cannot be saved due to a system error. Please try again.]
Mockup
TestRail: Results
Attachments
Issue Links
- is blocked by
-
MODKBEKBJ-576 GET Request: Make client id and secret key configurable
-
- Closed
-
-
MODKBEKBJ-579 PUT Request: Make client id and secret key configurable
-
- Closed
-
- relates to
-
UXPROD-2953 eholdings app | UI updates R2 2021
-
- Closed
-
- mentioned in
-
Page Loading...