Scott, Marvin, I'd like to get some feedback on this issue and patch. I think it resolves the issue Marvin was having with the LB more generally as well as fixes another specific issue I ran into.
Thanks, Bill [ https://issues.jasig.org/browse/NETC-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William G. Thompson, Jr. updated NETC-40: ----------------------------------------- Attachment: NETC-40.patch patch for this issue. > Redirect URL after successful login is incorrect when behind a load balancer > ---------------------------------------------------------------------------- > > Key: NETC-40 > URL: https://issues.jasig.org/browse/NETC-40 > Project: .NET CAS Client > Issue Type: Bug > Components: CAS Protocol Support > Affects Versions: NETC-1.0 > Environment: IIS behind a load balancer that is off loading SSL as > well. > Reporter: William G. Thompson, Jr. > Assignee: William G. Thompson, Jr. > Fix For: NETC-1.1-SNAPSHOT > > Attachments: NETC-40.patch > > > After successful authentication/validation the dotnetcas client is > constructing a URL for redirection to the targeted service based on the > request.uri. In cases were the request.uri is from the load balancer this > causes an incorrect URL to be constructed > after CAS redirect and authN cas redirects browser back to service > https://service.com/foo. > browser (GET https://service.com/foo?ST=######) -> LB (GET > http://service.com:443/foo?ST=#####) -> IIS(dotnetcas) > dotnetcas validates properly and then constructs a redirect to > http://service.com:443/foo rather then https://service.com/foo -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
