All about federation: cloud, bursting, storage, authn/z
So if anyone has a contact there, we can leverage that, or I (or someone else) can open a support request.
Yes, I just did that for our EBI repos, maybe better if someone else says pretty please from the Galaxy side.
Apparently they were getting a lot of bitcoin mining and related stuff.
Ok, I'll send an email. JBrowse folks just had all their builds fail for the same reason, heh.
Hi All, I'm new to the community. Hope it's not a silly question. I'm currently looking at using AzureAD als OpenID IDP for galaxy. I looked at: https://galaxyproject.org/authnz/config/oidc/ currently there are 6 custom providers AzureAD is not one of them. Is there any change AzureAD is added to the list or maybe an other approach that i can take?
Hi @robertbeudeker We think keycloak is a good option here and is something we use in practice to integrate with external identity providers (e.g. in the GVL). We connect Galaxy to KeyCloak via OIDC, and KeyCloak can in turn be connected to AzureAD.
@nuwang Thanks for the suggestion, I will look into that. Question about that. KeyCloak is not mentioned as a supported provider in Galaxy(https://galaxyproject.org/authnz/config/oidc/). How do you connect keycloak to Galaxy?