Shibboleth sp Apache - Artifact profile or POST profile depending on idp

[cneberg]

That worked thank you.



On Thu, May 8, 2025, 11:11 AM Cantor, Scott <cantor.2 at osu.edu> wrote:

> > In my case I don't mind hard coding the protocol binding to
> > POST for the site when I've already hard coded the idp to use for
> > the same site but I don't understand where to start.
>
> The best answer is don't, use POST across the board.
>
> You would have to define a custom SAML 2 <SessionInitiator> handler
> element at a different path, alongside the automatically generated one at
> /Login, and that one would have an acsIndex set in it to specify the ACS
> index of whichever of the two bindings was the "exception".
>
> The requireSessionWith content setting can reference a specific
> SessionInitiator to get a vhost to use it in place of the default one.
>
> The acsIndex is hard to know, but I believe the metadata generator
> endpoint would probably generate the same indexes it would know about
> internally, I'd at least start with that assumption.
>
> -- Scott
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250518/f054a3ff/attachment.htm>