Federated Single Logout issue.

[Vijitha Ekanayake]

Hi Scott,

Thanks a lot for the response.I used Shibboleth 2.4.4 and was able to
figure out the issue as <SingleLogoutService> endpoint not correctly
configured in the metadata file.


On Mon, Jul 13, 2015 at 11:30 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 7/13/15, 5:25 AM, "dev on behalf of Vijitha Ekanayake" <
> dev-bounces at shibboleth.net on behalf of ekvijitha at gmail.com> wrote:
>
> >Hi all,
> >
> >I am using Shibboleth IDP to provide authentication to access a web
> application.
> > I was able configure SSO via Shibboleth IDP and SSO works without any
> issue. But when it comes to SLO, it requires a profile handler to handle
> SLO request.
>
> You provided no information about which version is being used, and the
> only logout support in the IdP, which is very limited, is already
> configured by default.
>
> This is also a users list question, not a development question.
>
> > According to [1] I have configured profile handler relying-party.xml as
> following.
>
> That's already done by default.
>
> >But I'm getting Error Message: Message did not meet security requirements
> error when tying to SLO. Following exception[2] can be observed in
> idp-process log file of Shibboleth IDP. Can someone help me to figure out
> what am I missing when configuring SLO with Shibboleth IDP?
>
> I'm not going to follow up further on this list, but I would imagine the
> request wasn't signed, which is what the error in the log is telling you.
> (It's saying not authenticated, but the only authentication possibly in
> this scenario is generally signing.)
>
> -- Scott
>
>
>
>
> --
> To unsubscribe from this list send an email to
> dev-unsubscribe at shibboleth.net
>



-- 


*Best Regards, Vijitha Ekanayake*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150714/a962a4fb/attachment.html>