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
Both cloud authz and cloud storage are API-based functionalities. When designing these, we had a discussion on whether we should enable/disable APIs. Enabling or disabling some API endpoints is usually conceived as an anti-pattern, and, at least back then, neither Galaxy had any functionality to enable/disable some APIs nor we were aware of any API endpoints enabled/disabled on different instances. Therefore, we did not implement any means of enabling/disabling this UI, instead, we took the approach of implementing and merging the dependencies first. So, first OIDC, then authz, then cloud storage.
However, these APIs may not function properly (e.g., AWS will not work) if OIDC is not enabled, and that is the case on Main. Maybe this could be a motivation to commit to enabling OIDC on Main?
I believe this currently doesn't do anything, and this is confusing users (https://help.galaxyproject.org/t/galaxy-doesnt-allow-cloud-authorization-save-key-button-deactivated/4878).
The link to the documentation is broken as well.
@VJalili can you have a look at this please?
The text was updated successfully, but these errors were encountered: