[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-1877) Deny principal names that already act as group names
[
https://jira.jboss.org/jira/browse/JBPM-1877?page=com.atlassian.jira.plug...
]
Heiko Braun resolved JBPM-1877.
-------------------------------
Resolution: Done
This would require changes to the identity module schema, which cannot be done between
minor versions and shouldn't be considered for jbpm3 at all.
Deny principal names that already act as group names
----------------------------------------------------
Key: JBPM-1877
URL: https://jira.jboss.org/jira/browse/JBPM-1877
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: GWT Console 1.0.0 Beta1
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: GWT Console 1.0.0 CR1
It leads to unclear assignments. I.e. in the sample database exists a group
'user' and a principal 'user'.
If you assign a task (setActorId) to 'user', what should it be? A group or a
principal assignment?
--
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