Two NextCloud instances mixes up LDAP settings
-
- I have one NextCloud instance - configured with LDAP auth
- I setup another NextCloud instance, recover it from backup - it's configured to leave authorisation to the app itself.
As a result, second instance of NextCloud ends up having LDAP user and group backend module enabled as well, trying to authorise users against LDAP as well (and failing).
-
did you clone the second instance from the first one? If so, it should be then safe for that instance to disable the ldap plugin in nextcloud to avoid it looking up users there. Not sure what will happen with the users already in the database, marked as ldap users though.
-
@potemkin_ai said in Two NextCloud instances mixes up LDAP settings:
I setup another NextCloud instance, recover it from backup - it's configured to leave authorisation to the app itself.
Do you mean import here? If I understand correctly, you imported a backup which had cloudron user management enabled into an instance which does not have cloudron user management. If this is the case, after importing, you have to login as admin and disable the ldap settings manually.
-
Apologies for the delay!
@nebulon, nop it was fresh installation followed by recovery from the backup of ldap-disabled instance.
@girish , nop as well...Let me repeat my steps:
- install fresh NextCloud with ldap enabled
- install fresh NextCloud with ldap disabled
- recovered my old install of NextCloud, ldap disabled, to my new install - ldap-disabled
- got NextCloud ldap-enabled instance to my surprise...
And yeah, I had to login as admin and disable the ldap plugin.
-
@potemkin_ai in this whole procedure, is the first step of "install fresh NextCloud with ldap enabled" relevant?
got NextCloud ldap-enabled instance to my surprise...
I don't understand what this step means.
