[prev in list] [next in list] [prev in thread] [next in thread] 

List:       shibboleth-users
Subject:    Re: IdP 2.3.2 status
From:       Diego Figueroa <dfiguero () yorku ! ca>
Date:       2011-07-29 14:54:07
Message-ID: OFAF586F0B.904E66AF-ON852578DC.0051DBDB-852578DC.0051DBDD () yorku ! ca
[Download RAW message or body]

Thank you! That was it! I now get the proper status.

Diego.
-----users-bounces@shibboleth.net wrote: -----

To: General support list for questions related to Shibboleth <users@shibboleth.net>
From: Chad La Joie <lajoie@itumi.biz>
Sent by: users-bounces@shibboleth.net
Date: 07/29/2011 10:28AM
Subject: Re: IdP 2.3.2 status

a.b.c.d/255 wouldn't be a probably CIDR address anyways.

On 7/29/11 10:26 AM, Diego Figueroa wrote:
> Sorry I removed the /255 (single IP) when editing the address but it is there.
> 
> Diego.
> 
> -----users-bounces@shibboleth.net wrote: -----
> 
> To: General support list for questions related to Shibboleth <users@shibboleth.net>
> From: Chad La Joie <lajoie@itumi.biz>
> Sent by: users-bounces@shibboleth.net
> Date: 07/29/2011 10:24AM
> Subject: Re: IdP 2.3.2 status
> 
> Well, the allowed IPs, I think, needs to be specified as a CIDR block.
> So, add a /32 at the end and see if that helps.
> 
> On 7/29/11 10:22 AM, Diego Figueroa wrote:
> > 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@osu.edu> wrote: -----
> > 
> > To: "users@shibboleth.net" <users@shibboleth.net>
> > From: "Cantor, Scott E." <cantor.2@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@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
> > 
> 

-- 
Chad La Joie
http://itumi.biz
trusted identities, delivered
--
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net
--
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net


[prev in list] [next in list] [prev in thread] [next in thread]