On 10/14/21, 10:03 AM, "Padraic Renaghan via jetty-users" <jetty-users@eclipse.org> wrote:
> So is the normal setup with Apache using an add-on for SAML SSO, any > recommendations on which are best? I don't really pretend to claim "normal", I'm just opinionated, and inherently biased because I wrote a good chunk of the SAML 2.0 standard and I have led the Shibboleth Project for a long time. I'm deeply biased against OpenID Connect so I'm not going to go there. I'm simply saying that there's a ton of bad SAML code around, and that there are things that good code does (like support metadata and handle key changes properly) that are hard to find. That stuff is what makes implementations like Shibboleth "complex" but I don't apologize for that. "Screw key changes and trust" is "simple" but also deeply irresponsible. Using Apache has the benefit that it insulates things and allows flexibility so you can swap things in and out. > And on the Jetty side would it be looking for a special HTTP header that > the Apache side adds with the auth info. Or a cookie. Presumably > encrypted? You should be using the CGI interface to access data about the user, and that applies to any solution. Anything that embeds code in the app is doomed because you will be running it forever, apps are very hard to change politically even if not technically. Insulation from identity is the goal, it should be left to the container and web server (which is where you came in, asking about Jetty handling it for you). Shibboleth for example is designed to be replaced. It is not trying to trap you into running it forever. Nobody selling a library-based solution is able to claim that. -- Scott _______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
