<p dir="ltr">Hi Scott,</p>
<p dir="ltr">I am unable to find response for my following query in my mailbox. If you have already replied, could you pls point me to the response again ?</p>
<p dir="ltr">Thanks !!<br>
Amit Thukral</p>
<div class="gmail_quote">On Dec 23, 2014 10:30 PM, <<a href="mailto:dev-request@shibboleth.net">dev-request@shibboleth.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send dev mailing list submissions to<br>
<a href="mailto:dev@shibboleth.net">dev@shibboleth.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://shibboleth.net/mailman/listinfo/dev" target="_blank">http://shibboleth.net/mailman/listinfo/dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:dev-request@shibboleth.net">dev-request@shibboleth.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:dev-owner@shibboleth.net">dev-owner@shibboleth.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: dev Digest, Vol 42, Issue 26 (Amit Thukral)<br>
2. Re: Freeze v3 (Daniel Fisher)<br>
3. Re: dev Digest, Vol 42, Issue 26 (Cantor, Scott)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 22 Dec 2014 23:46:57 +0530<br>
From: Amit Thukral <<a href="mailto:amit.thukral403@gmail.com">amit.thukral403@gmail.com</a>><br>
Subject: Re: dev Digest, Vol 42, Issue 26<br>
To: "<a href="mailto:dev@shibboleth.net">dev@shibboleth.net</a>" <<a href="mailto:dev@shibboleth.net">dev@shibboleth.net</a>><br>
Message-ID:<br>
<CAJ62q=yofJCDwQnDxogJ9m2FkvH_Ub=+aAEiL13iaXh7kgAy=<a href="mailto:g@mail.gmail.com">g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Scott,<br>
<br>
Thanks for the previous response.<br>
I could find the previous issue and could fix it.<br>
Now the LogoutReuest received at SP-2 is fine and is being processed but<br>
still its not getting through.<br>
I am getting RequestDenied but unable to understand the reason for the<br>
same. Transaction logs say that the session was distroyed. Following are<br>
the request and response msgs:<br>
<br>
<br>
*<samlp:LogoutRequest ID="_cc692418-9396-4ba1-ae96-8c9411258463"<br>
Version="2.0" IssueInstant="2014-12-22T17:37:59.970Z"<br>
Destination="<a href="https://waf6sp1app1.com/Saml.sso/SLO/Redirect" target="_blank">https://waf6sp1app1.com/Saml.sso/SLO/Redirect</a><br>
<<a href="https://waf6sp1app1.com/Saml.sso/SLO/Redirect" target="_blank">https://waf6sp1app1.com/Saml.sso/SLO/Redirect</a>>"<br>
NotOnOrAfter="2014-12-22T18:37:59.970Z"<br>
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"><Issuer<br>
xmlns="urn:oasis:names:tc:SAML:2.0:assertion"><a href="https://sts.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/" target="_blank">https://sts.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/</a><br>
<<a href="https://sts.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/" target="_blank">https://sts.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/</a>></Issuer><NameID<br>
xmlns="urn:oasis:names:tc:SAML:2.0:assertion">3mZ23mGKvN_5-f8hG1k5r6nFNhdZvRmh5QjWGjQZDdE</NameID><samlp:SessionIndex>_c63793b5-8d60-4306-b56e-70c6669aebff</samlp:SessionIndex></samlp:LogoutRequest>*<br>
<br>
<br>
*<samlp:LogoutResponse xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"<br>
Destination="<a href="https://login.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/saml2" target="_blank">https://login.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/saml2</a><br>
<<a href="https://login.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/saml2" target="_blank">https://login.windows.net/3713ed32-ab1a-4a87-ab86-afdf9177ff06/saml2</a>>"<br>
ID="_91fb9446cda1b937fa8c34208b001457"<br>
InResponseTo="_cc692418-9396-4ba1-ae96-8c9411258463"<br>
IssueInstant="2014-12-22T17:38:14Z" Version="2.0"><saml:Issuer<br>
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"><a href="https://waf6sp1app1.com/samlsso" target="_blank">https://waf6sp1app1.com/samlsso</a><br>
<<a href="https://waf6sp1app1.com/samlsso" target="_blank">https://waf6sp1app1.com/samlsso</a>></saml:Issuer><samlp:Status><samlp:StatusCode<br>
Value="urn:oasis:names:tc:SAML:2.0:status:Requester"><samlp:StatusCode<br>
Value="urn:oasis:names:tc:SAML:2.0:status:RequestDenied"/></samlp:StatusCode><samlp:StatusMessage>Error<br>
processing<br>
request.</samlp:StatusMessage></samlp:Status></samlp:LogoutResponse>*<br>
<br>
<br>
*2014-12-22 09:38:14 INFO Shibboleth-TRANSACTION [1]: Destroyed session<br>
(applicationId: svc_3_pol1) (ID: _9c7176ee797f5ce3308406f1c0f7b7d1)*<br>
<br>
Thanks in advance for the help.<br>
Regards,<br>
Amit Thukral<br>
<br>
<br>
On Thu, Dec 18, 2014 at 10:30 PM, <<a href="mailto:dev-request@shibboleth.net">dev-request@shibboleth.net</a>> wrote:<br>
<br>
> Send dev mailing list submissions to<br>
> <a href="mailto:dev@shibboleth.net">dev@shibboleth.net</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://shibboleth.net/mailman/listinfo/dev" target="_blank">http://shibboleth.net/mailman/listinfo/dev</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:dev-request@shibboleth.net">dev-request@shibboleth.net</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:dev-owner@shibboleth.net">dev-owner@shibboleth.net</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of dev digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: Facing issue with Single Logout. (Cantor, Scott)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Thu, 18 Dec 2014 16:26:31 +0000<br>
> From: "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>><br>
> Subject: Re: Facing issue with Single Logout.<br>
> To: Shib Dev <<a href="mailto:dev@shibboleth.net">dev@shibboleth.net</a>><br>
> Message-ID: <<a href="mailto:59715D3C-80BE-4053-8B15-0C23D4919D50@osu.edu">59715D3C-80BE-4053-8B15-0C23D4919D50@osu.edu</a>><br>
> Content-Type: text/plain; charset="utf-8"<br>
><br>
> On 12/18/14, 4:17 PM, "Amit Thukral" <<a href="mailto:amit.thukral403@gmail.com">amit.thukral403@gmail.com</a>> wrote:<br>
> ><br>
> >shibd.log<br>
> ><br>
> >=========<br>
> >2014-12-17 21:55:29 ERROR XMLTooling.ParserPool [9] handleError: fatal<br>
> >error on line 1, column 1, message: An exception occurred!<br>
> >Type:UTFDataFormatException, Message:invalid byte 1 () of a 1-byte<br>
> >sequence.<br>
> >2014-12-17 21:55:29 ERROR Shibboleth.Listener [9]: error processing<br>
> >incoming message: XML error(s) during parsing, check log for specifics<br>
> ><br>
> ><br>
> >Is it because that the Logout Request reaching at SP-2 contains the<br>
> >entityID of SP-1 in issuer element which SP-2 has no knowledge of ?<br>
><br>
> No, it means what it says, the XML is invalid. The message was not encoded<br>
> correctly or was bad XML in the first place.<br>
><br>
> -- Scott<br>
><br>
><br>
> ------------------------------<br>
><br>
> --<br>
> To unsubscribe from this list send an email to<br>
> <a href="mailto:dev-unsubscribe@shibboleth.net">dev-unsubscribe@shibboleth.net</a><br>
><br>
> End of dev Digest, Vol 42, Issue 26<br>
> ***********************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://shibboleth.net/pipermail/dev/attachments/20141222/05795113/attachment-0001.html" target="_blank">http://shibboleth.net/pipermail/dev/attachments/20141222/05795113/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 22 Dec 2014 13:45:04 -0500<br>
From: Daniel Fisher <<a href="mailto:dfisher@vt.edu">dfisher@vt.edu</a>><br>
Subject: Re: Freeze v3<br>
To: Shib Dev <<a href="mailto:dev@shibboleth.net">dev@shibboleth.net</a>><br>
Message-ID:<br>
<<a href="mailto:CAFC6YwQ2Fsu8Q4McpjLFu7UdK3Z_O_7mbhpkSKjWfQXCN6VAYA@mail.gmail.com">CAFC6YwQ2Fsu8Q4McpjLFu7UdK3Z_O_7mbhpkSKjWfQXCN6VAYA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Mon, Dec 22, 2014 at 11:51 AM, Cantor, Scott <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br>
<br>
> On 12/22/14, 4:33 PM, "Daniel Fisher" <<a href="mailto:dfisher@vt.edu">dfisher@vt.edu</a>> wrote:<br>
><br>
> >On Fri, Dec 19, 2014 at 10:44 PM, Cantor, Scott<br>
> ><<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br>
> ><br>
> >V2 upgrade findings<br>
> >- out of the box, you do get a low level Spring error message and it's<br>
> >very noisy when it can't find the LDAP server cert, but it does say<br>
> >FileNotFound at the bottom of the mess<br>
> ><br>
> >Took an AI from this:<br>
> ><a href="https://github.com/vt-middleware/ldaptive/issues/19" target="_blank">https://github.com/vt-middleware/ldaptive/issues/19</a><br>
> ><<a href="https://github.com/vt-middleware/ldaptive/issues/19" target="_blank">https://github.com/vt-middleware/ldaptive/issues/19</a>><br>
> >Future versions of ldaptive may not be as noisy.<br>
><br>
> IIRC it's a Spring error failing to load the context, so I don't know that<br>
> it's anything you have control over.<br>
<br>
<br>
Ok. I know ldaptive emits an error log for every connection that fails. I<br>
thought that may be the culprit. Regardless, I'll take a pass at the log<br>
levels and make sure they're sane.<br>
<br>
--Daniel Fisher<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://shibboleth.net/pipermail/dev/attachments/20141222/858e787c/attachment-0001.html" target="_blank">http://shibboleth.net/pipermail/dev/attachments/20141222/858e787c/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 22 Dec 2014 18:50:22 +0000<br>
From: "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>><br>
Subject: Re: dev Digest, Vol 42, Issue 26<br>
To: Shib Dev <<a href="mailto:dev@shibboleth.net">dev@shibboleth.net</a>><br>
Message-ID: <<a href="mailto:5EC306F8-7A59-4055-A068-73217FA971C4@osu.edu">5EC306F8-7A59-4055-A068-73217FA971C4@osu.edu</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On 12/22/14, 6:16 PM, "Amit Thukral" <<a href="mailto:amit.thukral403@gmail.com">amit.thukral403@gmail.com</a>> wrote:<br>
<br>
>Now the LogoutReuest received at SP-2 is fine and is being processed but<br>
>still its not getting through.<br>
>I am getting RequestDenied but unable to understand the reason for the<br>
>same. Transaction logs say that the session was distroyed. Following are<br>
>the request and response msgs:<br>
<br>
I'm not going to go scouring source code for the status code unless there<br>
are no logs indicating why it handled the request that way.<br>
<br>
-- Scott<br>
<br>
<br>
------------------------------<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:dev-unsubscribe@shibboleth.net">dev-unsubscribe@shibboleth.net</a><br>
<br>
End of dev Digest, Vol 42, Issue 33<br>
***********************************<br>
</blockquote></div>