[FC-252] Fix Multitenancy bugs in addRoleConstraint

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.2
• Fix Version/s: 2.0.3
• Assignee: Shawn McKinney
• Reporter: Shawn McKinney
• Created: 25/Oct/18 15:57
• Updated: 25/Oct/18 15:57
• Resolved: 25/Oct/18 15:57

Description

In order for multitenancy to work, manager impl level code must set the context id after instantiating a model object.

e.g.

User user = new User( uRole.getUserId());
user.setContextId( contextId );

 

This is how the tenant is then passed down into DAO layer, in order to navigate to correct sub-tree. 

This issue fixes problems found in add and removeRoleConstraint methods in the AdminMgrImpl class.

 

Commits have already been made (and tested)...

 

removeRoleConstraint

https://github.com/apache/directory-fortress-core/commit/03dda314fcf278e8b7738d3471963a0a204cdaf9

addRoleConstraint:

https://github.com/apache/directory-fortress-core/commit/4d2a6130265dd23dcefc0d693398920f8dccfabc