Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 900302 (JBPAPP6-619)

Summary: Clustered SSO does not work
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Dominik Pospisil <dpospisi>
Component: Clustering, WebAssignee: sgilda
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.0.0CC: dpospisi
Target Milestone: ---   
Target Release: EAP 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-619
Whiteboard: eap6_clustering eap6_need_triage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-10 12:08:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sso.ear
none
standalone-ha.xml
none
standalone-ha.xml none

Description Dominik Pospisil 2012-04-26 15:44:25 UTC 
project_key: JBPAPP6

It seems to me that the clustered SSO is not working.

What I am seeing is that SSOCredentials are being correctly replicated from one node to onether, however they are never used by SSOClusterManager.

Associated testcase:
https://github.com/dpospisil/jboss-as/commit/17d54bd446ce904724b3f805a1de9efbb5364a25

Leaving priority to major as this is not yet confirmed.
Comment 1 Dominik Pospisil 2012-04-26 15:51:07 UTC 
Unless I am wrong, this is what is happening:

SSOCredentials are replicated correctly and stored in SSOClusterManager.cache, however the lookup(String ssoId) method fails to retreive it and always returns null even if the SSOCredentials are actually stored in the cache. I am seeing really weird behavior:

new CredentialKey(ssoId).equals(credentialCache.entrySet().iterator().next().getKey()) returns true

however

this.credentialCache.get(new CredentialKey(ssoId)) returns null
as well as
this.credentialCache.get(credentialCache.entrySet().iterator().next().getKey()) returns null
Comment 2 Dominik Pospisil 2012-04-26 15:55:06 UTC 
Attachment: Added: sso.ear
Comment 3 Dominik Pospisil 2012-04-26 16:10:22 UTC 
Cluster nodes configuration files.
Comment 4 Dominik Pospisil 2012-04-26 16:10:22 UTC 
Attachment: Added: standalone-ha.xml
Attachment: Added: standalone-ha.xml
Comment 5 Dominik Pospisil 2012-04-26 16:13:23 UTC 
Steps to reproduce:
1) start two instances of the AS using provided configuration files
2) deploy sso.ear on both servers
3) visit http://localhost:8080/web1/
4) log-in to web application using user1/password1
5) visit http://localhost:8180/web1/ - at this point, user should not be required to login again, but he is.
Comment 6 Rajesh Rajasekaran 2012-04-26 17:06:09 UTC 
Labels: Added: eap6_need_triage
Comment 7 Rajesh Rajasekaran 2012-04-26 17:26:53 UTC 
Labels: Removed: eap6_need_triage Added: eap6_clustering eap6_need_triage
Comment 8 Rajesh Rajasekaran 2012-04-26 17:27:43 UTC 
Link: Added: This issue is related to JBPAPP-7577
Comment 9 Dominik Pospisil 2012-04-27 09:01:20 UTC 
Link: Added: This issue relates to JBQA-6054
Comment 10 Paul Ferraro 2012-04-30 22:04:32 UTC 
Link: Added: This issue is incorporated by AS7-4681
Comment 11 Shelly McGowan 2012-05-01 13:48:50 UTC 
upstream fix will be in ER7.  Will verify after rebase.
Comment 12 Shelly McGowan 2012-05-03 16:17:58 UTC 
This fix will be in ER7.
Comment 13 Dominik Pospisil 2012-05-10 12:08:32 UTC 
Verified (ER7).
Comment 14 Anne-Louise Tangring 2012-11-05 17:45:08 UTC 
Docs QE Status: Removed: NEW