IdP 2.3.2 status
Diego Figueroa
dfiguero at yorku.ca
Fri Jul 29 15:22:28 BST 2011
I redeployed the war file, this time no modifications but now I get:
HTTP Status 401 -
type Status report
message
description This request requires HTTP authentication ().
Apache Tomcat/6.0.32
The idp-process.log contains:
08:18:26.642 - DEBUG [edu.internet2.middleware.shibboleth.idp.StatusServlet:121] - Attempting to authenticate client '130.xx.xx.xx'
So I would assume that at this point I just add my host to the IP address list
<param-name>AllowedIPs</param-name>
<param-value>127.0.0.1/32 ::1/128 130.xx.xx.xx</param-value>
I restart but again I get the same error:
08:23:03.151 - DEBUG [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:323] - LoginContext key cookie was not present in request
08:23:03.151 - DEBUG [edu.internet2.middleware.shibboleth.idp.ui.ServiceContactTag:177] - No relying party, nothing to display
Diego.
-----"Cantor, Scott E." <cantor.2 at osu.edu> wrote: -----
To: "users at shibboleth.net" <users at shibboleth.net>
From: "Cantor, Scott E." <cantor.2 at osu.edu>
Date: 07/28/2011 02:34PM
Subject: Re: IdP 2.3.2 status
On 7/28/11 2:17 PM, "Diego Figueroa" <dfiguero at yorku.ca> wrote:
>Just tried this, got the same error.
>
>Any other ideas why the cookie might not be present?
There is no cookie. You have something causing the IdP to try and
authenticate requests to the handler, but a standard install does not do
that. You have to have broken something in web.xml, I would think.
-- Scott
--
To unsubscribe from this group, send email to
users+unsubscribe at shibboleth.net
More information about the users
mailing list