Hi Vahid, I think you've hit on a really good point that makes me lean toward the current custos integration approach instead of PSA so we have the flexibility to handle this use case.
Marlon was right to suggest we sleep on it. I'm inclined to not go the PSA route. We can always revisit in the future if we find that Custos authentication can fit in the PSA abstraction; it may be a good way to simplify Custos integration for Python based gateways. To address the Galaxy concern about well known urls, I was thinking that we can create a Python Custos client library that would only define these urls for now but that would over time become a real client to the Custos API. Thanks, Marcus > On 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
smime.p7s
Description: S/MIME cryptographic signature
