[GH-ISSUE #1018] [BUG] Cannot update display name of a user #370

Closed
opened 2026-02-27 08:16:54 +03:00 by kerem · 0 comments
Owner

Originally created by @Gucek-Malinek on GitHub (Oct 29, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/1018

Describe the bug
When I save user information, more precisely modified 'Display name' (in edit mode not create a new one), I receive an error in the user panel management:

Errors: [updateUser:2:3: Internal error: `User attribute name display_name doesn't exist in the schema, yet was attempted to be removed from the database`]

To Reproduce

  1. Go to user list
  2. Click on login
  3. Change 'Display name' value
  4. Click 'Save changes'

Expected behavior
'Display name' will be saved correct.

Logs

ERROR    │     ┕━ 🚨 [error]:  | error: Internal error: `User attribute name display_name doesn't exist in the schema, yet was attempted to be removed from the database`

Additional context
However display_name exists in the schema and in the database.

Environment: LLDAP dockered version: lldap/lldap:2024-10-24-debian + MySQL backend

Originally created by @Gucek-Malinek on GitHub (Oct 29, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/1018 **Describe the bug** When I save user information, more precisely modified 'Display name' (in edit mode not create a new one), I receive an error in the user panel management: ``` Errors: [updateUser:2:3: Internal error: `User attribute name display_name doesn't exist in the schema, yet was attempted to be removed from the database`] ``` **To Reproduce** 1. Go to user list 2. Click on login 3. Change 'Display name' value 4. Click 'Save changes' **Expected behavior** 'Display name' will be saved correct. **Logs** ``` ERROR │ ┕━ 🚨 [error]: | error: Internal error: `User attribute name display_name doesn't exist in the schema, yet was attempted to be removed from the database` ``` **Additional context** However `display_name` exists in the schema and in the database. Environment: LLDAP dockered version: lldap/lldap:2024-10-24-debian + MySQL backend
kerem 2026-02-27 08:16:54 +03:00
  • closed this issue
  • added the
    bug
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#370
No description provided.