You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.Configure ldap server 1 in the owncloud ldap settings
2.Configure a different ldap server 2 in the owncloud ldap settings to which you cannot establish the connection with
3.Make sure the configuration active is deactivated for the server to which you cannot establish a connection with
4.Run the command line occ user:sync "OCA\User_LDAP\User_Proxy" to sync the users
Expected behaviour
The occ user:sync command should run without error
Actual behaviour
The occ user:sync command is returning an error
In Connection.php line 532:
[OCA\User_LDAP\Exceptions\BindFailedException]
When deactivating the configuration active for the server to which you cannot establish a connection with, the error disappears.
The text was updated successfully, but these errors were encountered:
Akidxx
changed the title
"BindFailedException" error when running the occ user:sync "OCA\User_LDAP\User_Proxy
Bug in configuration active settings
Dec 10, 2020
Reproducer step 3 appears to be identical to the setting that avoids the issue:
"Make sure the configuration active is deactivated ..." -- "When deactivating the configuration active ..."
Steps to reproduce
1.Configure ldap server 1 in the owncloud ldap settings
2.Configure a different ldap server 2 in the owncloud ldap settings to which you cannot establish the connection with
3.Make sure the configuration active is deactivated for the server to which you cannot establish a connection with
4.Run the command line
occ user:sync "OCA\User_LDAP\User_Proxy"
to sync the usersExpected behaviour
The occ user:sync command should run without error
Actual behaviour
The occ user:sync command is returning an error
When deactivating the configuration active for the server to which you cannot establish a connection with, the error disappears.
ownCloud version: 10.5.0
LDAP Integration app version: 0.15.2
Bug reproduced by me
The text was updated successfully, but these errors were encountered: