Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

PUT Request: Make client id and secret key configurable

Priority

Labels

Environment

None

Template

None

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.

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.]

Rough mockup

Development Team

Spitfire

Release

None

Story Points

Sprint

Attachments

1
  • 08 Apr 2021, 04:32 PM

Confluence content

mentioned on

Checklist

hide

TestRail: Results

Activity

Show:
Oleksandr_Dekin
updated the Fix versionsOctober 7, 2021 at 7:06 PM
None
3.8.0
Khalilah Gambrell
updated the Linked IssuesMay 17, 2021 at 11:18 PM
None
This issue relates to UXPROD-2953
Khalilah Gambrell
changed the StatusMay 6, 2021 at 1:15 PM
In Review
Closed
Khalilah Gambrell
updated the ResolutionMay 6, 2021 at 1:15 PM
None
Done
Pavlo Smahin
changed the StatusMay 3, 2021 at 12:59 PM
In Code Review
In Review
Pavlo Smahin
changed the StatusApril 29, 2021 at 5:00 PM
In Progress
In Code Review
Pavlo Smahin
updated the RankApril 28, 2021 at 12:47 PM
None
Ranked lower
Pavlo Smahin
updated the SprintApril 28, 2021 at 12:47 PM
None
eHoldings Sprint 113
Pavlo Smahin
changed the AssigneeApril 28, 2021 at 12:22 PM
Unassigned
Pavlo Smahin
Pavlo Smahin
changed the StatusApril 28, 2021 at 12:22 PM
Open
In Progress
Oleksandr_Dekin
updated the Story PointsApril 15, 2021 at 12:56 PM
None
3
Khalilah Gambrell
updated the RankApril 8, 2021 at 4:46 PM
None
Ranked higher
Khalilah Gambrell
updated the DescriptionApril 8, 2021 at 4:38 PM
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.   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.
*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. *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.] *Rough mockup* !screenshot-1.png|thumbnail!
Khalilah Gambrell
added an AttachmentApril 8, 2021 at 4:32 PM
None
screenshot-1.png
Khalilah Gambrell
updated the Linked IssuesApril 8, 2021 at 4:17 PM
None
This issue links to "Page (FOLIO Wiki)"
Khalilah Gambrell
updated the Linked IssuesApril 8, 2021 at 4:17 PM
None
This issue blocks UIEH-1112
Khalilah Gambrell
updated the Linked IssuesApril 8, 2021 at 4:17 PM
None
This issue clones MODKBEKBJ-576
Khalilah Gambrell
created the IssueApril 8, 2021 at 4:17 PM
Done

Details

Assignee

Reporter

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 8, 2021 at 4:17 PM
Updated October 7, 2021 at 7:06 PM
Resolved May 6, 2021 at 1:15 PM
TestRail: Cases
TestRail: Runs

Flag notifications