dev Digest, Vol 42, Issue 26

[Amit Thukral]

Hi Scott,

Thanks for the previous response.
I could find the previous issue and could fix it.
Now the LogoutReuest received at SP-2 is fine and is being processed but
still its not getting through.
I am getting RequestDenied but unable to understand the reason for the
same. Transaction logs say that the session was distroyed. Following are
the request and response msgs:


*<samlp:LogoutRequest ID="_cc692418-9396-4ba1-ae96-8c9411258463"
Version="2.0" IssueInstant="2014-12-22T17:37:59.970Z"
Destination="https://waf6sp1app1.com/Saml.sso/SLO/Redirect
<https://waf6sp1app1.com/Saml.sso/SLO/Redirect>"
NotOnOrAfter="2014-12-22T18:37:59.970Z"
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"><Issuer
xmlns="urn:oasis:names:tc:SAML:2.0:assertion">https://sts.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/
<https://sts.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/></Issuer><NameID
xmlns="urn:oasis:names:tc:SAML:2.0:assertion">3mZ23mGKvN_5-f8hG1k5r6nFNhdZvRmh5QjWGjQZDdE</NameID><samlp:SessionIndex>_c63793b5-8d60-4306-b56e-70c6669aebff</samlp:SessionIndex></samlp:LogoutRequest>*


*<samlp:LogoutResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
Destination="https://login.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/saml2
<https://login.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/saml2>"
ID="_91fb9446cda1b937fa8c34208b001457"
InResponseTo="_cc692418-9396-4ba1-ae96-8c9411258463"
IssueInstant="2014-12-22T17:38:14Z" Version="2.0"><saml:Issuer
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://waf6sp1app1.com/samlsso
<https://waf6sp1app1.com/samlsso></saml:Issuer><samlp:Status><samlp:StatusCode
Value="urn:oasis:names:tc:SAML:2.0:status:Requester"><samlp:StatusCode
Value="urn:oasis:names:tc:SAML:2.0:status:RequestDenied"/></samlp:StatusCode><samlp:StatusMessage>Error
processing
request.</samlp:StatusMessage></samlp:Status></samlp:LogoutResponse>*


*2014-12-22 09:38:14 INFO Shibboleth-TRANSACTION [1]: Destroyed session
(applicationId: svc_3_pol1) (ID: _9c7176ee797f5ce3308406f1c0f7b7d1)*

Thanks in advance for the help.
Regards,
Amit Thukral


On Thu, Dec 18, 2014 at 10:30 PM, <dev-request at shibboleth.net> wrote:

> Send dev mailing list submissions to
>         dev at shibboleth.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://shibboleth.net/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
>         dev-request at shibboleth.net
>
> You can reach the person managing the list at
>         dev-owner at shibboleth.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Facing issue with Single Logout. (Cantor, Scott)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 18 Dec 2014 16:26:31 +0000
> From: "Cantor, Scott" <cantor.2 at osu.edu>
> Subject: Re: Facing issue with Single Logout.
> To: Shib Dev <dev at shibboleth.net>
> Message-ID: <59715D3C-80BE-4053-8B15-0C23D4919D50 at osu.edu>
> Content-Type: text/plain; charset="utf-8"
>
> On 12/18/14, 4:17 PM, "Amit Thukral" <amit.thukral403 at gmail.com> wrote:
> >
> >shibd.log
> >
> >=========
> >2014-12-17 21:55:29 ERROR XMLTooling.ParserPool [9] handleError: fatal
> >error on line 1, column 1, message: An exception occurred!
> >Type:UTFDataFormatException, Message:invalid byte 1 () of a 1-byte
> >sequence.
> >2014-12-17 21:55:29 ERROR Shibboleth.Listener [9]: error processing
> >incoming message: XML error(s) during parsing, check log for specifics
> >
> >
> >Is it because that the Logout Request reaching at SP-2 contains the
> >entityID of SP-1 in issuer element which SP-2 has no knowledge of ?
>
> No, it means what it says, the XML is invalid. The message was not encoded
> correctly or was bad XML in the first place.
>
> -- Scott
>
>
> ------------------------------
>
> --
> To unsubscribe from this list send an email to
> dev-unsubscribe at shibboleth.net
>
> End of dev Digest, Vol 42, Issue 26
> ***********************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20141222/05795113/attachment.html