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 r
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
HI Alex,
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
On Aug 19, 2014, at 7:52 AM, 706826 wrote:
> I want to put access control on the BRMS repository/project access, so that
> developer-A can only work on repository-A. We have a central BRMS which has
> one repository per project. We have 20 projects and have 20 repository, one
> for each project.
I want to put access control on the BRMS repository/project access, so that
developer-A can only work on repository-A. We have a central BRMS which has
one repository per project. We have 20 projects and have 20 repository, one
for each project.
We strongly want that user working on project-A must
