[ https://jira.jboss.org/jira/browse/JBPM-1993?page=com.atlassian.jira.plug... ] Heiko Braun updated JBPM-1993: ------------------------------ Affects Version/s: jBPM 4.0.0 Alpha2 -- 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/JBPM-1993?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1993: ------------------------------ Priority: Critical (was: Major) -- 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/JBPM-1993?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1993: ----------------------------------- in jbpm 4 we should centralize all access to the identity component. this spi will be the jbpm pluggability point to replace identity components. then we should bind this initially and by default to the new jboss identity component: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184053#... But we must have a clear SPI (IdentitySession) so that all jBPM usage of an identity component can be plugged with a customized implementation. This will be necessary if users have another identity component then the jboss identity component. -- 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