[
http://jira.jboss.com/jira/browse/JBPORTAL-1849?page=all ]
Sohil Shah updated JBPORTAL-1849:
---------------------------------
Fix Version/s: 2.6.5 Final
(was: 2.6.4 Final)
Priority: Minor (was: Major)
downgraded to minor because installing the CAS or JOSSO authentication server on the same
server as one of the portal nodes within a SSO Federation is not a deal breaker.
It would be a showstopper if other independent portal nodes in the federation could not
use the authentication server unless it was co-installed. That would actually
wouldn't be SSO.
Eventually, a web service based communication needs to be created between the portal nodes
and the authentication server so that the Authentication Server can be installed as a
completely standalone physical machine. Right now the communication is JMX based
Make the CAS and JOSSO integrations location independent
--------------------------------------------------------
Key: JBPORTAL-1849
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1849
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Portal Identity
Affects Versions: Identity-1.0, 2.6.2 Final, 2.6.3 Final
Reporter: Sohil Shah
Assigned To: Sohil Shah
Priority: Minor
Fix For: 2.6.5 Final
Current integration uses Mbean services for integration requiring the CAS and JOSSO
server to be co-located in the same AS as the portal server.
Make this integration such that CAS/JOSSO servers can be deployed on completely different
machines, even physically
--
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