Done
Details
Details
Assignee
Michelle Suranofsky
Michelle SuranofskyReporter
Yauhen Viazau
Yauhen ViazauDevelopment Team
EBSCO - FSE
Release
Sunflower (R1 2025)
Tester Assignee
Yauhen Viazau
Yauhen ViazauRCA Group
TBD
Priority
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created August 16, 2024 at 12:22 PM
Updated last week
Resolved last week
Description
Overview: GET request to https://edge-crs-sandbox2.int.aws.folio.org/courses/reserves fails with a 403 response
Steps to reproduce:
Send the GET request to the following endpoint:
<<Edge URL>>/courses/reserves
Add "Authorization" header with value of edge user API key
Expected result: Response has 200 status code
Response body includes “reserves” attribute containing an array of reserve objects (each with “id”, “courseListingId” and other attributes)
Actual result: Response with 403 Status and the following response body:
Additional info:
This issue was fixed in previously on evrk2 by adding the following capabilities to the edge role:
"course-reserves-storage.reserves.collection.get"
"course-reserves-storage.courselistings.reserves.collection.get"
What is required now is to ensure this role will have all necessary capabilities by default (seemingly a DevOps job)
NOT reproducible for FSE Dry run 1 ECS
Also reproducible on https://eureka-bugfest-ramsons.int.aws.folio.org/ (and not on ECS - https://eureka-bugfest-ramsons-consortium.int.aws.folio.org)