Handler dropping port from service url passed by CAS Auth Filter

[Mackay, Rob]

Micheal
	Thank you - that was the exact problem. 
Rob Mackay

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Michael A Grady
Sent: Thursday, February 27, 2014 8:10 PM
To: Shib Users
Subject: Re: Handler dropping port from service url passed by CAS Auth Filter


On Feb 27, 2014, at 6:04 PM, Cantor, Scott wrote:

> On 2/27/14, 5:23 PM, "Mackay, Rob" <Rob.Mackay at ellucian.com> wrote:
> 
>> Does anyone have an idea which class constructs the CAS redirect URL ?
>> I have been walking through code today and it is not terribly 
>> apparent exactly where this is happening.
> 
> You haven't said anything about what you're doing to integrate CAS 
> here, but there is nothing in Shibboleth that has anything to do with 
> CAS right now, so I suspect if you're looking at Shibboleth, you're 
> pretty much looking in the wrong place.
> 
> -- Scott


Given the URLs you have, I presume you are integrating Shib with CAS using the "RemoteUser" approach rather than the shib-cas-authenticator. That is documented here:

 https://wiki.jasig.org/display/CASUM/Shibboleth-CAS+Integration

Note the CAS Conttext Parameters listed there:

<!-- For CAS client support -->
<context-param>
  <param-name>serverName</param-name>
  <param-value>${idp.hostname}</param-value>
</context-param>

If the IdP is at an alternate port, you'll need to include that port as part of the ${idp.hostname}, so presumably you need for that:

 testlp5.ellucian.com:444

--
Michael A. Grady
Senior IAM Consultant, Unicon, Inc.

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