Ldap sync issue

[y0d4a]

hi, i have installed wekan with snap.
have problem with AD sync.
I was change AD account and now he cannot connect, said creds. wrong, but creds. are fine.
also i get this error:

'E11000 duplicate key error collection: wekan.cronHistory index: intendedAt_1_name_1 dup key: { : new Date(1588108080000), : "LDAP_Sync" }',

how to delete that key?

[xet7]

@y0d4a

With nosqlbooster GUI connect to server port localhost 27019 (optionally through SSH) and remove it from wekan database cronHistory collection/table.

[y0d4a]

to remove collections "cronHistory" ?

[xet7]

Do not remove collection, only delete all contents of it.

db.cronHistory.deleteMany({})

[y0d4a]

i saw now, when i list the content.
sorry, did not work on mongo until now... :)
But after that, this error is gone, but still dont work, said that is invalid creds. but creds. 100% correct

[ERROR] InvalidCredentialsError: 80090308: LdapErr: DSID-0C090446, comment: AcceptSecurityContext error, data 52e, v2580

[xet7]

https://github.com/wekan/wekan/wiki/LDAP

https://github.com/wekan/wekan/issues?q=is%3Aissue+52e+is%3Aclosed

[y0d4a]

yep, exactly that i followed...

[y0d4a]

also see that more them have same issue, unsolved:
wekan/ldap#52

[xet7]

Well, you maybe need to unset and set ldap sync settings again.

sudo snap unset wekan ldap...
sudo snap set wekan ldap...

[xet7]

That's because you did delete that data from database.

[y0d4a]

still unable to set....
is it possible to drop all ldap collection and recreate?

[xet7]

@y0d4a

Backup first.

It would be better to test on other install of Wekan first, how to get LDAP working, and then apply those changes to your original install.

You can try to drop ldap collection, but do not drop users collection, because those user IDs are connected to board IDs who is where.

And it's very easy to get Wekan messed up by directly editing database.

In theory, you could export all boards to Wekan JSON, and import to Wekan from previous export, but it's possible that not all board data is exported/imported in that process, there could be some open issues about that.

[y0d4a]

i am sorry, it was my fault, i did not enter full CN, was missing one character :(
all is fine, thank you for time!