Open K8Sewell opened 3 months ago
Is setting up 9 a problem?
Would want someone to be alerted if this is accessed. We SHOULDN'T hit these, and if we CAN, there should be an alert.
Let's review at a future date and make a new table with what should be monitored. Check in Thursday.
Restrict now - https://collections.library.yale.edu/management/api/download /management/api/permission_requests /management/api/permission_sets /management/api/user
YCO can be done now, need to wait for an asset for OwP - Image | /iiif/2/15239177/full/!200,200/0/default.jpg Manifest | /manifests/15238597 OwP Request | /catalog/2005512/request_form OwP Terms | /catalog/2005512/terms_and_conditions OwP Confirmation | /catalog/2005512/request_confirmation PDF | /pdfs/15238597.pdf TIFF Download | /download/tiff/15014414 TIFF Staged | /download/tiff/15014414/staged
Links to synthetic checks that will open an SNOW INC with DevOps if they fail:
https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-95E0887886D4368E?gtf=-2h&gf=all https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-23E365E8A8F5C7D7?gtf=-2h&gf=all https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-6F42A9E35BBB13F1?gtf=-2h&gf=all https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-CB64A0ECF060B18B?gtf=-2h&gf=all
OwP = Open with Permission object permissions YCO = Yale Community Only permissions
Provide complete URLs for OwP and YCO objects and break out OwP into a second ticket
parent oid: 10090497 child oid: 1400485
Image - https://collections.library.yale.edu/iiif/2/1400485/full/!200,200/0/default.jpg Manifest - https://collections.library.yale.edu/manifests/10090497 PDF - https://collections.library.yale.edu/pdfs/10090497.pdf TIFF Download - https://collections.library.yale.edu/download/tiff/1400485 TIFF Staged - https://collections.library.yale.edu/download/tiff/1400485/staged
I get a 200 back for the /staged URL, is that expected? All others I get 401
npg26 ~/playground ▶ curl -s -I https://collections.library.yale.edu/download/tiff/1400485/staged |grep HTTP
HTTP/2 200
Image - https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-84757DEC1AFD6877?gtf=-2h&gf=all Manifest - https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-57248EF5FADD9503?gtf=-2h&gf=all PDF - https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-12E068618DBD12E0?gtf=-2h&gf=all TIFF Download - https://nhd42358.live.dynatrace.com/ui/http-monitor/HTTP_CHECK-BF5FC34BFB92EF6E?gtf=-2h&gf=all
Summary
Use table of restricted URLs from tickets #2912 and #2911 to create monitoring and synthetic tests for ensuring URLs behave as expected.
Acceptance Criteria