Closed sshetenhelm closed 3 months ago
PRs ready for review: Blacklight - https://github.com/yalelibrary/yul-dc-blacklight/pull/1032/ Camerata - https://github.com/yalelibrary/yul-dc-camerata/pull/382 Management - https://github.com/yalelibrary/yul-dc-management/pull/1418
Not working - taking back to in progress
I did not add the token variable to all the places it needed to be. This PR fixes that - https://github.com/yalelibrary/yul-dc-camerata/pull/384
Confirmed that auth token present in blacklight and management tasks on AWS yet still getting an 'unauthorized' response instead of displaying the request form as expected. Taking back to in progress.
We can just put the header on requests so management knows it's blacklight. We don't need them on responses. Blacklight will trust that it's talking to management for this ticket.
Updated the PRs and they are ready for review
PRs ready for review:
https://github.com/yalelibrary/yul-dc-blacklight/pull/1043 https://github.com/yalelibrary/yul-dc-management/pull/1426
Behaviors work as expected. Will promote to UAT.
Appears to be working as expected for me in UAT :)
Story Right now communications are "open" between Mgmt APIs and Blacklight. It might be good to have a security token of some kind passed with the requests. The Mgmt APIs are blocked by the firewall [note: need to review/confirm the setup] and should be unreachable but this would be a second line of defense.
This work should take place after #2876 (merging demo with main) but prior to release)
Acceptance
Authorization
HTTP header