Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 86, eHoldings Sprint 87
-
3
-
Spitfire
Description
Support retrieval of KB credentials entry user is assigned to by the following method:
GET /eholdings/user-kb-credential
The payload of the response should contain information about particular KB credentials entry.
Sample response body:
{
"id": "2ffa1940-2cf6-48b1-8cc9-5e539c61d93f",
"type": "credentials",
"attributes": {
"name": "University of Massachusetts - Amherst",
"apiKey": "XXXX",
"url": "YYYY",
"customerId": "ZZZZ"
},
"metadata": {
"createdDate": "2020-03-17T15:22:04.098",
"updatedDate": "2020-03-17T15:23:04.098+0000",
"createdByUserId": "1f8f660e-7dc9-4f6f-828f-96284c68a250",
"updatedByUserId": "6893f51f-b40c-479d-bd78-1704ab5b802b",
"createdByUsername": "john_doe",
"updatedByUsername": "jane_doe"
}
}
More details can be found in the dedicated section of "Spike: MODKBEKBJ-390 - describe design for "Single tenant multiple EBSCO KBs" scenario"
Requirements
- endpoint returns an existing KB credentials entry, a user is assigned to.
- returns an error if a user was not assigned to any KB credentials entry
Acceptance Criteria
- the endpoint created and works according to the requirements
- the endpoint is covered with unit tests
- API tests added to cover endpoint
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-1994 eholdings app | Single Tenant w/ Multiple Libraries Support
-
- Closed
-
- is defined by
-
MODKBEKBJ-390
Spike: describe design for "Single tenant multiple EBSCO KBs" scenario
-
- Closed
-
- is required by
-
UIEH-871
eholdings app: Access denied messaging
-
- Closed
-
- relates to
-
MODKBEKBJ-393 Spike "Single tenant + KBs": Managing KB Credentials in MOD KB EBSCO module
-
- Closed
-