[
http://jira.jboss.com/jira/browse/JBPORTAL-1849?page=comments#action_1240... ]
Guy M. Spillman, Jr. commented on JBPORTAL-1849:
------------------------------------------------
I believe these should also be split into separate responsibilities.
1. Redirect to, and then consume information from the SSO facility, regardless of what
authentication mechanism are configured on the SSO facility.
2. A plug-in to the SSO facility to allow other SSO users to authenticate against JBoss
Portal Identity Management.
Right now, these two are explicitly dependent on each other. This is a problem because if
I don't want non-JBoss Portal clients to authenticate against JBoss Portal Identity
Management, I'm out of luck.
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