You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@lpalbou Thank you for adding this--I still hadn't fully process those announcements.
These sites still work without HTTPS, correct? As we circle around and start treating with geneontology/go-site#53 more seriously, we can coordinate a common way forward.
I just checked; yes the API works also in HTTP but the site currently has an autoredirect http -> https through cloudfront. Should an issue happened, this is an easy fix.
That would be nice indeed to have all services running HTTPS. I would start by low level services such as GOLr, blazegraph & barista. Once those are HTTPS, we can proceed with the UIs tools
The following announcement could impact both the GO-CAM website and the GO-CAM API as they are working with AWS SSL: https://aws.amazon.com/blogs/security/how-to-prepare-for-aws-move-to-its-own-certificate-authority/
At the moment, this doesn't seem to affect us, but will have to be monitored.
The text was updated successfully, but these errors were encountered: