[rules-users] BRMS 6 Access Permissions Configuration - Not Restricting Custom Roles

[Maciej Swiderski]

Roles assigned to repositories or OUs are on top of the application roles (admin, user, developer, analyst, etc) so to be able to logon to kie-wb you’ll need to have one of the application roles and then roles specific to repository and/or OU. 
There is a mechanism to map different application roles but they are global to installation of kie-wb meaning that whenever you change it it will apply to all OUs and repositories on given instance of kie-wb.

So to make it to work make sure that your users are assigned to one or more application roles (admin, user, developer, analyst) and it should work just fine.

Maciej
On 24 sie 2014, at 07:52, Zahid Ahmed <zahid.ahmed at emirates.com> wrote:

> HI Alex,
> 
> The issue is still not resolved. And my real problem is how to associate my custom roles to permissions (Kindly refer to below example and attachment in last reply.)
> 
> I have created custom roles and assigned those roles to user in user manament db. Then I assigned the new custom roles to the Organizational Units (OUs), one OU per project.
> 
> Kindly see attachment for clarification.
> 
> And I created following custom roles
> *Project A and OU A*
> 
> *Custom Role:                 Permission*
> cs_A_admin                      Can Create, Can deploy, Can delete, Can view
> cs_A_developer                 Can Create, Can delete, Can View, Can Update
> cs_A_analyst                    Can Create, Can View, Can Update
> cs_A_business                  Can View
> 
> *Project B and OU B*
> *Custom Role:                 Permission*
> cs_B_admin                      Can Create, Can deploy, Can delete, Can view
> cs_B_developer                 Can Create, Can delete, Can View, Can Update
> cs_B_analyst                    Can Create, Can View, Can Update
> cs_B_business                  Can View
> 
> 
> My question is where to map role and permissions ? where to do these configurations. CLI tool help does not say anything about this.
> 
> *Custom Role:                 Permission*
> cs_admin                      Can Create, Can deploy, Can delete, Can view
> cs_developer                 Can Create, Can delete, Can View, Can Update
> cs_analyst                    Can Create, Can View, Can Update
> cs_business                  Can View
> 
> Authorization_Issue_2.png
> <http://drools.46999.n3.nabble.com/file/n4030691/Authorization_Issue_2.png>  
> 
> 
> 
> --
> View this message in context: http://drools.46999.n3.nabble.com/BRMS-6-Access-Permissions-Configuration-Not-Restricting-Custom-Roles-tp4030679p4030691.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
> 
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20140827/08c049d3/attachment.html