mismatch in ACS URL - port included in SP request to IdP

[Kohlhaas, James]

I determined that the issue was due to the query string parameters I had defined to initiate a lazy session with the IDP.  I included the port number in the login handler and the target parameter.  Once I removed the port everything began to work as expected.  

Thanks for the asistance!

James Kohlhaas

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, October 31, 2012 2:04 PM
To: Shib Users
Subject: Re: mismatch in ACS URL - port included in SP request to IdP

I verified how the code works, and basically something in what you posted isn't what you're actually using, provided that you don't have something else unusual in play like a handlerURL setting with an absolute URL with port specified, which I'll assume isn't the case.

The way it decides to add the port to the redirect is by looking at the scheme and the port and adding the port if it's non-default. That means it thinks the scheme is http, not https. What you posted wouldn't result in that being the case, so something's not what you think it is.

Specifically, there's no way you have scheme="https" in the <Site> element, or at least not in the one that it's actually mapping the request into. So I'd look at that first.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net