"tom.baeyens(a)jboss.com" wrote : "jbpid_group_id_._._unit_._._sales-dept" is a very nasty id that you generate. | | so the real point is actually: shouldn't we switch to user-provided id's for the groups as well. just like we do with the users ? | | what was the reason that we didn't do that ? I think we can have an approach to this issue. we will use what it uses for groupId, candidate-group now. but we need to document the format for this groupId: it is: | String groupId = groupType != null ? groupType + "." + groupName : groupName; | in this case, the groupId format is maintained by jBPM, and not identity component dependent. so if users/developers switch to other identity provider, they must conform this rule. In this case, we don't need to make any changes, the only one thing is just to document it? What do you think? -Jeff View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237811#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...