[EXTERNAL] RE: SLO with SAML question.

[Ernie Kinsey]

Scott,

OK, thanks, that means I’m at least looking at the right thing.  It’s the same application, and I know not to point it at the SAML logout endpoint, so the question is: what should I point it at?  This is where I’m lost.  Is there something I need to add to the relying party, for example?  The vendor’s no help, and if there’s some standard answer to how to direct the logout from the application to Shibboleth and cause it to log out of there as well as out of the application, I’m not finding it so far (or am finding it and don’t know what I’m looking at.)

Thanks again,
Ernest K. Kinsey, Jr.
Central Piedmont Community College
Charlotte, NC.

On 4/23/18, 12:21 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

    > Which I’ve enabled, but still no joy.  I suspect I’m not doing something very
    > basic here and don’t know if there’s a better place I should be looking for
    > guidence on how to do what I’m trying to do, namely, implement a SAML2
    > SLO for a vendor-hosted application.  If there’s a better place, or places, I
    > should be looking, or if there are other suggestions, please let me know – as
    > always, any assistance is appreciated.

    As far as your question is concerned, there are two properties, both noted, trackSPSessions and secondaryServiceIndex. The first is just a given and the second is SAML SLO specific.

    If this is the same application, the question is immaterial, the point of my answer is that it's not *doing* SAML logout. Nothing you do is going to change that and you MUST NOT point it at the SAML logout endpoint, it will simply fail.

    -- Scott

    --
    For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
    To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


________________________________

This e-mail, including any attachments, is intended only for the addressee's use and may contain confidential and proprietary information. If you are not the intended recipient, you are hereby notified that any retention, dissemination, reproduction, or use of the information contained in this e-mail is strictly prohibited. If you have received this e-mail by error, please delete it and immediately notify the sender. Thank you for your cooperation.