cancel
Showing results for 
Search instead for 
Did you mean: 

Only one admin left when using LDAP and NTLM

_sax
Champ in-the-making
Champ in-the-making
We managed to get LDAP and NTLM SSO working with our installation of 2.1 Community.

Since our ECM is administered by several admins we put them into the
<property name="adminUsers">
section of custom-authority-services-context.xml. This worked flawlessly, until we started to use LDAP and NTLM configuration. Since then, we only have the original "admin" user left as being able to use the administration console. While using LDAP we made sure, that we cleared all children before import and that the same user names existed in the LDAP-directory as they did in our local alfresco user database.

Is this a known problem, maybe with a known solution to it?
1 REPLY 1

_sax
Champ in-the-making
Champ in-the-making
We retested this behaviour with a fresh installation of 2.9b.
After LDAP and NTLM were active, all of the admins that were configured in  /tomcat/shared/classes/alfresco/extension/custom-authority-services-context.xml were granted admin rights.

But as soon, as the old repository was imported, only the user admin was still able to administer Alfresco.
If he was uncommented
        <property name="adminUsers">
            <set>
             <!– <value>admin</value> –>
             <value>someotheruser</value>
            </set>
       </property>
its rights vanished; if reactivated, he got its admin function back. But for the other users (which were successfully imported and could work flawlessly), this didn't have any effect. They stayed with the rights of a normal user.
The same users worked as admins before the import.

Is there something we could try regarding this behaviour? Maybe there is a chance to edit the user-rights via a full export in the xml-files of the acp that is holding all information about the users' rights?