Details
-
Type:
Improvement
-
Status: Reopened
-
Severity:
High
-
Resolution: Unresolved
-
Affects Version/s: 5.0.4 GA, 5.0.5 GA
-
Fix Version/s: None
-
Component/s: Administration, Migrator, Security
-
Labels:
-
Notice:
-
Sprint:Vodka Finalization, 5.x Required Defects
Description
After importing migrated content from 4.8.x that was configured to use MS AD the following two properties are added to the applicationContext-spring-ldap.properties
- These properties were added during migration:
adminRole=cn\=Administrator,ou\=roles
adminUser=uid\=admin,ou\=users
There are two problems with these two lines:
Problem 1 as described in BISERVER-11443
Problem 2 even after adding a valid username to adminUser and restarting the server the adminUser will not have Administrator privileges; this is because we still do not have the appropriate MS AD admin role to be mapped to the Pentaho's Administrator role.
Since we are migrating from 4.8.3 we should be able to get the admin role from the following file:
/pentaho-solutions/system/pentaho.xml from the following tag:
<admin-role>ADPentahoAdmin</admin-role>
Please see attached 4.8.3 pentaho.xml
so instead of adding:
adminRole=cn\=Administrator,ou\=roles
we should add it as:
adminRole=cn\=ADPentahoAdmin
PractiTest Integration
Attachments
Issue Links
- is related to
-
BISERVER-11443 404 error in 5.0.x when running import utility from 4.8.x server using MS AD
-
- Closed
-