[
http://jira.jboss.com/jira/browse/JBAS-1900?page=all ]
Brian Stansberry updated JBAS-1900:
-----------------------------------
Summary: Clustered webapp shouldn't require ClusteredSingleSignOn
(was: Clustered webapp shouldn't require ClusteredSingleSignon?)
Workaround Description: I haven't tested this, so buyer beware. The request notes
that using ClusteredSSO is not an option due to different sets of users for different
webapps. Set the "requireReauthentication" attribute in the
ClusteredSingleSignOnValve to "true". Each request will then be reauthenticated
by the security layer, which should prevent users from one set accessing resources meant
for another set.
Workaround: [Workaround Exists]
Suggested workaround added.
Clustered webapp shouldn't require ClusteredSingleSignOn
--------------------------------------------------------
Key: JBAS-1900
URL:
http://jira.jboss.com/jira/browse/JBAS-1900
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, Security
Affects Versions: JBossAS-4.0.2 Final
Reporter: Stan Silvert
Assigned To: Brian Stansberry
Priority: Minor
Fix For: JBossAS-4.0.6.CR1
A customer had three webapps. The set of users for each webapp is different. So, they
don't want single signon behavior. They do want HttpSessionReplication to take care
of the credentials so that the user doesn't need to sign on when redirected to another
server. It was found that we needed to enable clustered single signon to get this to
work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira