The Guvnor5 migration tool, will migrate one package to a project in Guvnor6. I should be adding project scoped security, in the UI. If the remove GIT connector is used, such as with team syncing, we cannot provide anything lower than repository level. But note you can have as many repositories as you like, and if necessary one project per repository.At the moment 6.0 authenticates users from a properties file (drools-wb) or with JACC (kie-drools-wb and kie-wb).
Uberfire, the underlying workbench library, supports a finer grained permissions model however we are still discussing requirements for 6.0.
Previous "package" level permissions may become project level (as 6.0 allows for multiple projects to be authored side-by-side and as dependencies of one and other).
Feedback from the community would be great :-)
On 30 May 2013 16:07, "Dean Whisnant" <dean@basys.com> wrote:_______________________________________________Maybe it’s too early to ask this question, but in reviewing 6.0 beta 2 I didn’t see how user security would be managed.
In 5.1.1 we have 100+ packages with 100+ users assigned various roles from read only to authoring. Our packages are hierarchical in that we have an overarching and intermediary set that everyone can view, and then individual packages that a user may have authoring privileges.
Is there a similar sense in the new framework?
Thanks
Dean
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users