Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 86
-
3
-
Spitfire
Description
Provide a way to update details of a user associated with KB credentials by introducing an endpoint:
PUT /eholdings/kb-credentials/<credentialsId>/users/<userId>
Payload of the request should contain user details and credentialsId. User details are limited to:
- user id
- user name
- first name
- middle name
- last name
- patron group
Sample request body:
{
"user":
{
"id": "1f8f660e-7dc9-4f6f-828f-96284c68a25",
"credentialsId": "2ffa1940-2cf6-48b1-8cc9-5e539c61d93f",
"firstName": "John",
"middleName": "William",
"lastName": "Doe",
"patronGroup": "Staff",
"userName": "john_doe"
}
}
More details can be found in the dedicated section of "Spike: MODKBEKBJ-390 - describe design for "Single tenant multiple EBSCO KBs" scenario"
Requirements
- details of user associated with particular KB credentials can be updated (this does not include credentialsId/userId - it cannot be changed)
- an error is returned if user association is not found by credentialsId + userId
Acceptance Criteria
- the endpoint created and works according to the requirements
- the endpoint is covered with unit tests
- API tests updated respectively
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-857
New/Edit Assign users page: Allow a user to assign a user(s) to an EBSCO KB
-
- Closed
-
- relates to
-
MODKBEKBJ-394 Spike "Single tenant + KBs": Assigning users to KB credentials
-
- Closed
-