[GH-ISSUE #924] [BUG]firstName and lastName are treated as attributes #336

New issue

Closed

opened 2026-02-27 08:16:43 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 08:16:43 +03:00

Owner

Originally created by @innomatica on GitHub (Jun 28, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/924

Describe the bug
I'm not 100% sure it is a bug or a design decision but firstName and lastName fields are treated as attributes with names first_name and last_name. This behaviour is consistent regardless of the methods (Web, LDAP, or GraphQL).

I'm using a docker image (2024-06-16-alpine).

To Reproduce
Steps to reproduce the behavior:

Go to /users/ on the web console
Click on 'Create a user'
Enter values including First name (say John) and Last name (say Doe)
Back to /users/ and see First name and Last name are empty
Use graphql to query the user and see the values are populated as attributes

        {
            "id": "john.doe",
            "email": "john.doe@example.com",
            "displayName": "John Doe",
            "firstName": "",
            "lastName": "",
            "avatar": null,
            "creationDate": "2024-06-24T13:41:21.947054920+00:00",
            "uuid": "571a5944-56e9-3234-a51c-b8ade55b433e",
            "attributes": [
                {
                    "name": "first_name",
                    "value": [
                        "John"
                    ]
                },
                {
                    "name": "last_name",
                    "value": [
                        "Doe"
                    ]
                }
            ],
            "groups": [
                {
                    "id": 3,
                    "displayName": "lldap_strict_readonly",
                    "creationDate": "2024-06-24T13:39:02.227155013+00:00",
                    "uuid": "9450a72a-dba6-38d8-890c-7939db5fcc01"
                }
            ]
        }

Expected behavior
firstName and lastName are treated as fields as they are defined. Or remove the fields from the schema.

Originally created by @innomatica on GitHub (Jun 28, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/924 **Describe the bug** I'm not 100% sure it is a bug or a design decision but `firstName` and `lastName` fields are treated as attributes with names `first_name` and `last_name`. This behaviour is consistent regardless of the methods (Web, LDAP, or GraphQL). I'm using a docker image (2024-06-16-alpine). **To Reproduce** Steps to reproduce the behavior: 1. Go to `/users/` on the web console 2. Click on 'Create a user' 3. Enter values including First name (say John) and Last name (say Doe) 4. Back to `/users/` and see First name and Last name are empty 5. Use graphql to query the user and see the values are populated as attributes ``` { "id": "john.doe", "email": "john.doe@example.com", "displayName": "John Doe", "firstName": "", "lastName": "", "avatar": null, "creationDate": "2024-06-24T13:41:21.947054920+00:00", "uuid": "571a5944-56e9-3234-a51c-b8ade55b433e", "attributes": [ { "name": "first_name", "value": [ "John" ] }, { "name": "last_name", "value": [ "Doe" ] } ], "groups": [ { "id": 3, "displayName": "lldap_strict_readonly", "creationDate": "2024-06-24T13:39:02.227155013+00:00", "uuid": "9450a72a-dba6-38d8-890c-7939db5fcc01" } ] } ``` **Expected behavior** firstName and lastName are treated as fields as they are defined. Or remove the fields from the schema.