LDAP debug flag produces no logs

[digikwal]

Summary

Enabling Developer Tools → LDAP Debug does not produce useful debug output for LDAP login attempts in Wiki.js 2.5.312.

Environment

• Wiki.js: 2.5.312 (requarks/wiki:2)
• PostgreSQL
• LDAP strategy configured via Admin UI

What I observed

• LDAP strategy initializes correctly.
• LDAP debug flag is enabled.
• Failed LDAP login attempts do not generate expected LDAP debug logs.
• In practice, debug output is too limited to troubleshoot real LDAP login failures from logs.

Source-level findings

The resolver-level LDAP debug check is tied to:

args.strategy === 'ldap'

But args.strategy is the strategy record key (UUID), not literal ldap.
This can suppress expected debug logging even when LDAP debug is enabled.

root@notes:~/wiki# docker exec -it wiki-db-1 psql -U wikiuser -d wikidb -c 'select "key", "strategyKey", "displayName", "isEnabled", "order" from authentication order by "order";'
                 key                  | strategyKey | displayName | isEnabled | order 
--------------------------------------+-------------+-------------+-----------+-------
 local                                | local       | Local       | t         |     0
 5a9ae9cf-385b-4609-9359-15cf0b197685 | ldap        | LDAP / IPA  | t         |     1
(2 rows)

root@notes:~/wiki# docker exec -it wiki-db-1 psql -U wikiuser -d wikidb -c "select \"key\", \"strategyKey\", \"displayName\" from authentication where \"strategyKey\" = 'ldap';"
                 key                  | strategyKey | displayName 
--------------------------------------+-------------+-------------
 5a9ae9cf-385b-4609-9359-15cf0b197685 | ldap        | LDAP / IPA
(1 row)

Why this matters

The UI option says it logs detailed LDAP/AD login debug info, but real-world behavior can be effectively silent, making LDAP troubleshooting more difficult.

root@notes:~/wiki# docker logs -f wiki-wiki-1 
Loading configuration from /wiki/config.yml... OK
2026-04-23T10:57:07.775Z [MASTER] info: =======================================
2026-04-23T10:57:07.778Z [MASTER] info: = Wiki.js 2.5.312 =====================
2026-04-23T10:57:07.778Z [MASTER] info: =======================================
2026-04-23T10:57:07.778Z [MASTER] info: Initializing...
2026-04-23T10:57:08.382Z [MASTER] info: Using database driver pg for postgres [ OK ]
2026-04-23T10:57:08.388Z [MASTER] info: Connecting to database...
2026-04-23T10:57:08.438Z [MASTER] info: Database Connection Successful [ OK ]
2026-04-23T10:57:09.323Z [MASTER] info: Loading GraphQL Schema...
2026-04-23T10:57:10.230Z [MASTER] info: GraphQL Schema: [ OK ]
2026-04-23T10:57:10.465Z [MASTER] info: HTTP Server on port: [ 3000 ]
2026-04-23T10:57:10.490Z [MASTER] info: HTTP Server: [ RUNNING ]
2026-04-23T10:57:10.661Z [MASTER] info: No new analytics providers found: [ SKIPPED ]
2026-04-23T10:57:10.678Z [MASTER] info: Loaded 21 authentication strategies: [ OK ]
2026-04-23T10:57:10.697Z [MASTER] info: No new comment providers found: [ SKIPPED ]
2026-04-23T10:57:10.712Z [MASTER] info: No new editors found: [ SKIPPED ]
2026-04-23T10:57:10.737Z [MASTER] info: No new loggers found: [ SKIPPED ]
2026-04-23T10:57:10.799Z [MASTER] info: No new renderers found: [ SKIPPED ]
2026-04-23T10:57:10.828Z [MASTER] info: No new search engines found: [ SKIPPED ]
2026-04-23T10:57:10.866Z [MASTER] info: No new storage targets found: [ SKIPPED ]
2026-04-23T10:57:10.867Z [MASTER] info: Checking for installed optional extensions...
2026-04-23T10:57:10.881Z [MASTER] info: Optional extension git is installed. [ OK ]
2026-04-23T10:57:10.887Z [MASTER] info: Optional extension pandoc was not found on this system. [ SKIPPED ]
2026-04-23T10:57:10.893Z [MASTER] info: Optional extension puppeteer was not found on this system. [ SKIPPED ]
2026-04-23T10:57:10.894Z [MASTER] info: Optional extension sharp was not found on this system. [ SKIPPED ]
2026-04-23T10:57:10.900Z [MASTER] info: Authentication Strategy Local: [ OK ]
2026-04-23T10:57:10.955Z [MASTER] info: Authentication Strategy LDAP / IPA: [ OK ]
2026-04-23T10:57:11.639Z [MASTER] info: (COMMENTS/DEFAULT) Initializing...
2026-04-23T10:57:11.640Z [MASTER] info: (COMMENTS/DEFAULT) Initialization completed.
2026-04-23T10:57:11.655Z [MASTER] info: (SEARCH/POSTGRES) Initializing...
2026-04-23T10:57:11.669Z [MASTER] info: (SEARCH/POSTGRES) Initialization completed.
2026-04-23T10:57:11.691Z [MASTER] info: (STORAGE/DISK) Initializing...
2026-04-23T10:57:11.692Z [MASTER] info: (STORAGE/DISK) Initialization completed.
2026-04-23T10:57:11.699Z [MASTER] info: Purging orphaned upload files...
2026-04-23T10:57:11.700Z [MASTER] info: Syncing locales with Graph endpoint...
2026-04-23T10:57:11.701Z [MASTER] info: Fetching latest updates from Graph endpoint...
2026-04-23T10:57:11.747Z [MASTER] info: Purging orphaned upload files: [ COMPLETED ]
Loading configuration from /wiki/config.yml... OK
2026-04-23T10:57:11.965Z [MASTER] info: Fetching latest updates from Graph endpoint: [ COMPLETED ]
2026-04-23T10:57:11.969Z [JOB] info: Rebuilding page tree...
2026-04-23T10:57:12.152Z [MASTER] info: Pulled latest locale updates for English from Graph endpoint: [ COMPLETED ]
2026-04-23T10:57:12.158Z [MASTER] info: Syncing locales with Graph endpoint: [ COMPLETED ]
2026-04-23T10:57:12.532Z [JOB] info: Using database driver pg for postgres [ OK ]
2026-04-23T10:57:12.620Z [JOB] info: Rebuilding page tree: [ COMPLETED ]
2026-04-23T11:12:11.748Z [MASTER] info: Purging orphaned upload files...
2026-04-23T11:12:11.749Z [MASTER] info: Purging orphaned upload files: [ COMPLETED ]
2026-04-23T11:27:11.751Z [MASTER] info: Purging orphaned upload files...
2026-04-23T11:27:11.752Z [MASTER] info: Purging orphaned upload files: [ COMPLETED ]

Suggested direction

Make LDAP debug logging strategy-type aware (strategyKey === 'ldap') and broaden failure-path logging so failed LDAP attempts consistently produce actionable logs.

File, line, issue

• server/graph/resolvers/authentication.js:105
  Issue: LDAP debug logging is gated by args.strategy === 'ldap'. In real setups, args.strategy is often the auth record key (UUID), so the LDAP debug branch is skipped and no useful log is emitted.

Proposed solution

• Replace the direct string check with a lookup on the configured strategy and test strategyKey
• Log when strategy lookup fails while ldapdebug is enabled.
• Include args.strategy in the warning context for easier traceability.

} catch (err) {
  // LDAP Debug Flag
  if (WIKI.config.flags.ldapdebug) {
    try {
      const strategy = await WIKI.models.authentication.getStrategy(args.strategy)

      if (strategy?.strategyKey === 'ldap') {
        WIKI.logger.warn(`LDAP LOGIN ERROR (c1) [strategy=${args.strategy}]: `, err)
      } else if (!strategy) {
        WIKI.logger.warn(`LDAP DEBUG: strategy lookup failed [strategy=${args.strategy}]`)
      }
    } catch (lookupErr) {
      WIKI.logger.warn(`LDAP DEBUG: strategy lookup exception [strategy=${args.strategy}]: `, lookupErr)
    }
  }

  return graphHelper.generateError(err)
}