Sorry, I was not clear. This is related to the discussion we had about what a Galaxy user sees on Galaxy login page? is it a button saying "login with keycloak", or a list of institutes that they can choose from (similar to Globus)? I think we agreed on the latter approach. Login via institutes is provided by CILogon through keycloak to Galaxy. Therefore, to bypass keycloak and CILogon page and head directly to the institutes login page from Galaxy, you would use a "hint" attribute to let keycloak/CILogon which institute (IdP/backend) user has chose.
_____________ *Vahid Jalili, *Ph.D. Computational Biologist Computational Biology Institute Oregon Health and Science University 2730 SW Moody Ave, KCRB #3103.20, OHSU-RLSB Dock 61, Portland, OR, USA 97201 Skype ID: v.jalili On Wed, Feb 27, 2019 at 11:26 PM Thejaka Amila J Kanewala < [email protected]> wrote: > Hi Vahid, > > I did not quite follow you. What do you mean by "which CILogon backend"? If > my memory is correct, CILogon has one backend. > > Thanks > Thejaka > > On Tue, Feb 26, 2019 at 4:26 PM Vahid Jalili <[email protected]> > wrote: > > > Hi All, > > > > One of the points may worth consideration before this integration is that > > how it works with "hint endpoints": telling Keycloak which backend of > > CILogon to be used hence to bypass keycloak/CILogon page and visit > directly > > to the IdP's login page? > > > > Best, > > _____________ > > *Vahid Jalili, *Ph.D. > > Postdoctoral Scholar > > Computational Biology Institute > > Oregon Health and Science University > > 2730 SW Moody Ave, KCRB #3103.20, > > OHSU-RLSB Dock 61, > > Portland, OR, USA 97201 > > Skype ID: v.jalili > > > > > -- > Best Regards, > Thejaka Amila Kanewala, PhD > https://github.com/thejkane/agm >
