[
https://jira.jboss.org/jira/browse/JBPM-1923?page=com.atlassian.jira.plug...
]
Thomas Diesler updated JBPM-1923:
---------------------------------
Description: * SSO: Customers have their own SSO solution but it is unclear to them
how to hook it into jBPM's Identity manager. Their solution t is not LDAP-based, it
is their own custom form of WS with HTTP POST, no WSDL. This is also an immediate
concern. It is likely they'll need some form of "mapper" for roles to
swimlanes and more flexibility in this whole area. (was: * SSO: Goldman has their own
SSO solution but it is unclear to them how to hook it into jBPM's Identity manager.
Their solution t is not LDAP-based, it is their own custom form of WS with HTTP POST, no
WSDL. This is also an immediate concern. It is likely they'll need some form of
"mapper" for roles to swimlanes and more flexibility in this whole area. )
Integrate with JBoss SSO
------------------------
Key: JBPM-1923
URL:
https://jira.jboss.org/jira/browse/JBPM-1923
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Productization
Reporter: Thomas Diesler
* SSO: Customers have their own SSO solution but it is unclear to them how to hook it
into jBPM's Identity manager. Their solution t is not LDAP-based, it is their own
custom form of WS with HTTP POST, no WSDL. This is also an immediate concern. It is
likely they'll need some form of "mapper" for roles to swimlanes and more
flexibility in this whole area.
--
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