Bug 793695 (JBEPP-771) - CAS integration fails if EPP server is set up with SSL
Summary: CAS integration fails if EPP server is set up with SSL
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-771
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.1.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.1.DEV01
Assignee: Thomas Heute
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-07 09:15 UTC by Martin Weiler
Modified: 2012-02-28 16:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
- EPP 5.1, CAS setup as per Chapter 14.6.2 of the Reference Guide - SSL connector enabled for EPP instance
Last Closed: 2011-04-20 11:29:45 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 793823 0 high CLOSED Upgrade SSO component to 1.0.2-epp-GA 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEPP-771 0 Major Closed CAS integration fails if EPP server is set up with SSL 2012-11-16 16:54:06 UTC

Internal Links: 793823

Description Martin Weiler 2011-01-07 09:15:02 UTC 
Affects: Release Notes
Help Desk Ticket Reference: https://na7.salesforce.com/500A0000003zkwT
project_key: JBEPP

Upon trying to login from an EPP 5.1 instance with SSL enabled (https://localhost:8443/portal/), the ticket validation fails with the following error:

Caused by: org.jasig.cas.client.validation.TicketValidationException: 
                ticket 'ST-1-k9kY9cdZBmol5FCNvnBj-cas' does not match supplied service.  The original service was 'https://localhost:8443/portal/private/classic' and the supplied service was 'http://localhost:8443/portal/private/classic'.

        at org.jasig.cas.client.validation.Cas20ServiceTicketValidator.parseResponseFromServer(Cas20ServiceTicketValidator.java:73)
        at org.jasig.cas.client.validation.AbstractUrlBasedTicketValidator.validate(AbstractUrlBasedTicketValidator.java:188)
        at org.gatein.sso.agent.cas.CASAgent.validateTicket(CASAgent.java:84)
        at org.gatein.sso.agent.GenericSSOAgent.processSSOToken(GenericSSOAgent.java:108)
        at org.gatein.sso.agent.GenericSSOAgent.doGet(GenericSSOAgent.java:73)
Comment 2 Sohil Shah 2011-04-01 15:06:51 UTC 
This issue is fixed on the trunk while fixing another issue.
Comment 3 Sohil Shah 2011-04-01 15:10:39 UTC 
accidentally assigned to me
Comment 5 Thomas Heute 2011-04-20 11:28:43 UTC 
Link: Added: This issue relates to JBEPP-898
Comment 6 Thomas Heute 2011-04-20 11:29:45 UTC 
Will be fixed by upgrading SSO component to 1.0.2-epp-GA
Comment 7 Scott Mumford 2011-08-09 03:02:43 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Removed: Prior to this fix, CAS ticket validation failed when the EPP instance was set up with SSL. This has been fixed and CAS ticket validation works fine with http and https. Added: Prior to this release, CAS ticket validation failed when the JBoss Enterprise Portal Platform instance was set up with SSL. This has been fixed with an upgrade to the SSO component. CAS ticket validation now works as expected with http and https addresses.
Note You need to log in before you can comment on or make changes to this bug.