Providing different login pages per applications using the same SP/IdP

Cantor, Scott cantor.2 at osu.edu
Thu May 3 21:45:48 BST 2012


On 5/3/12 4:41 PM, "Jason Cameron" <jbkc85 at gmail.com> wrote:
>
>I am currently working with one Service Provider that is providing
>Shibboleth among 2-5 applications.  Though each one of these applications
>I can set up with an ApplicationOverride, they all point back to the
>-same- IdP as well.  Most of the information I have found relates to
>changing the IdP login page (css/imagery) based on the EntityID (Service
>Provider), where I am interested if its possible to change the login page
>based on the ApplicationID from the SP or any other passed variable.

That isn't possible. The only unit of policy in SAML is the entityID. The
rest is internal to the SP. If you want there to be differences they can,
should, and must have different entityIDs.

It would help if you could clarify what wasn't clear on the
NativeSPApplicationModel page, since I took pains to address that, or
thought I did, but it was covering a lot of ground and may be focusing on
other aspects.

-- Scott



More information about the users mailing list