HelpDesk 1.1.9-1/1.1.13-1 — TypeError on login (Argument #4 $user_group must be array, null given)

15 views
Skip to first unread message

htc one

unread,
Jul 13, 2026, 4:10:08 AM (10 days ago) Jul 13
to RCDevs Security

Environment:

  • WebADM Enterprise Edition 2.4.14-2, RHEL 9
  • HelpDesk 1.1.9-1 (also reproduced on 1.1.13-1)
  • LDAP backend: RCDevs internal directory, base o=Root

Issue:
Login to HelpDesk webapp succeeds (LDAP password OK, user resolved, group resolved), but a PHP Fatal error occurs immediately after, resulting in a blank page.

Steps already verified:

  • User dan.vdi is directly a member (member attribute) of the configured Admin Group cn=helpdesk,dc=WebADM (groupOfNames)
  • Both user and group objects are Activated in WebADM
  • Admin Groups setting correctly references cn=helpdesk,dc=WebADM
  • User Search Scopes set to o=Root
  • Cleared System & Application Caches, Application Sessions, reloaded WebADM Configurations, restarted webadm service, server — no change
  • Other webapps (User Self-Registration, User Self-Service Desk) work normally

Log output:

[HelpDesk:E2BXL6OT] Resolved LDAP user: cn=dan.vdi,o=Root (cached) [HelpDesk:E2BXL6OT] Resolved LDAP groups: helpdesk (cached) [HelpDesk:E2BXL6OT] LDAP password Ok PHP Fatal error: Uncaught TypeError: helpdesk_start_session(): Argument #4 ($user_group) must be of type array, null given, called in /opt/webadm/webapps/helpdesk/www/login_uid.php on line 140 and defined in /opt/webadm/webapps/helpdesk/lib/helpdesk_common.php:91 Stack trace: #0 /opt/webadm/webapps/helpdesk/www/login_uid.php(140): helpdesk_start_session('dan.vdi', 'Default', 'cn=dan.vdi,o=Ro...', NULL) #1 {main} thrown in /opt/webadm/webapps/helpdesk/lib/helpdesk_common.php on line 91 Thanks!

Yoann Traut (RCDevs)

unread,
Jul 13, 2026, 4:15:48 AM (10 days ago) Jul 13
to RCDevs Security

Hello,

Could you update WebADM, OpenOTP, and Helpdesk to their latest versions and check whether you are able to reproduce the issue?

Based on the information you provided, we suspect the issue originates from WebADM/OpenOTP, as those components were not updated when you tested with the latest version of the Helpdesk application.

Kind regards,

Reply all
Reply to author
Forward
0 new messages