Wiki: cannot Login with LDAP / Active Directory

Created on 7 Sep 2020  路  12Comments  路  Source: Requarks/wiki

Actual behavior

After the newest Update (2.5.117) when trying to log in using the LDAP / Active Directory login, an Error is occuring: "undefined passed as a property in argument #0 for 'where' operation. Call skipUndefined() method to ignore the undefined values."

Expected behavior

It logs me into the Server per LDAP / Active Directory

os: Linux - Ubuntu (bionic) 18.04 x64
Version: 2.5.117
Database engine: PostgreSQL 10.14

Best Regards
KleepX :)

bug

Most helpful comment

Fixed by 78417524b3d00adcb6f5596a4bdf4dc0287dff39

A new release is currently compiling and will be published soon. (v2.5.126)

All 12 comments

I have a same problem
2020-09-07T07:22:14.546Z [MASTER] warn: LDAP LOGIN ERROR (c1): undefined passed as a property in argument #0 for 'where' operation. Call skipUndefined() method to ignore the undefined values.

Hi all,

I have same problem. It's a big problem.

undefined passed as a property in argument #0 for 'where' operation. Call skipUndefined() method to ignore the undefined values.

os: Linux - Debian 10
Version: 2.5.117
Database engine: mariadb-server 1:10.3.23 (Galera Cluster)

Hello, i was going to open an issue when i just saw this one, i made the upgrade twice to be sure it wasn't my mistake but no... looks to be a bug in version 2.5.117
Other identification method like keycloak is working fine

Running into the same issue after an upgrade the ldap login is not working anymore

I have the same problem after upgrading from 2.5.107.

I also have the same issue with the latest docker version.

I have the same error after upgrading to 2.5.117 from 2.4.107
PostgresSQL: 11.7
Node.js: 10.21.0
Debian: 10 x64

Now I am stuck at 2.5.117 with no ldap login, because downgrade doesnt work.
Local Login works fine...

Same.

PostgresSQL: 12.0
Node.js: 12.13.0
OS : Windows Server 2016

Issue is being investigated.

@AlmightyMiniMoose And this is why you're supposed to have a database backup before attempting any upgrade.

Hi, same issue after upgrading from 2.4.x to the newest 2.5.x from today. I run wiki.js in a virtual machine on my VMware ESXi. Made a snapshot before upgrading. Restored snapshot in less than 5 minutes. Old system up and running again, so no big deal. Maybe this is an idea for further updates for some of the users here who are now not able to use their wiki.js ...

also clicking ldap multiple times in the login page yields errors in the console

Fixed by 78417524b3d00adcb6f5596a4bdf4dc0287dff39

A new release is currently compiling and will be published soon. (v2.5.126)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

gruesomehit picture gruesomehit  路  4Comments

ghost picture ghost  路  3Comments

touhoku-japan picture touhoku-japan  路  3Comments

thinkh picture thinkh  路  4Comments

ccolella-mdc picture ccolella-mdc  路  3Comments