[ 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 -- 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

[ http://jira.jboss.com/jira/browse/JBPORTAL-1849?page=comments#action_1241... ] Sohil Shah commented on JBPORTAL-1849: -------------------------------------- Guy- I agree with both your points. However, JBoss Portal does not drive the design decisions of SSO Frameworks. Every SSO Framework has its own architecture, and JBoss Portal takes the approach of integrating with most widely adopted open frameworks out there With CAS and JOSSO, although you get point #1I don't believe hot swapping Identity Connectors is supported. This is kind of the bane of old Hub and Spoke Frameworks. JBoss SSO on the other hand is completely authentication agnostic. There is no redirect to a Hub and back architecture. It only serves as a Cross Domain SSO Session orchestrator in a nutshell. OpenSSO has a hub and spoke model but not sure if Identity Connector is swappable based on client. In short, JBoss Portal takes the approach of integrating with whatever architecture the Framework dictates -- 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

[ http://jira.jboss.com/jira/browse/JBPORTAL-1849?page=all ] Thomas Heute updated JBPORTAL-1849: ----------------------------------- Fix Version/s: 2.7.0 Beta1 (was: 2.7.0 Alpha1) -- 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

[ https://jira.jboss.org/jira/browse/JBPORTAL-1849?page=com.atlassian.jira.... ] Sohil Shah updated JBPORTAL-1849: --------------------------------- Fix Version/s: 2.7.0 Final (was: 2.7.0 CR1 ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPORTAL-1849?page=com.atlassian.jira.... ] Sohil Shah updated JBPORTAL-1849: --------------------------------- Fix Version/s: (was: 2.7.1 Final) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira