Starting userldap id instead "jovyan"

Why when I log in authenticating against ldap, the user is not created? On the other hand, why is “jovyan” set and not the ldap user id, and why does it look like this?
image

Thank you for helping me, I need it to be as follows:
gdelris@jupyter-gdelris

This is mi config.yaml, It works for authentication:
hub:
config:
Authenticator:
enable_auth_state: true
JupyterHub:
authenticator_class: ldapauthenticator.LDAPAuthenticator
LDAPAuthenticator:
server_address: 10.72.134.241
server_port: 389
lookup_dn: true
auth_state_attributes: [uidNumber,gidNumber,uid]
lookup_dn_search_user:
lookup_dn_search_password:
user_search_base: ou=Usuarios,dc=ambientesbc,dc=lab
user_attribute: sAMAccountName
lookup_dn_user_dn_attribute: cn
escape_userdn: false
create_user_home_dir: True
create_user_home_dir_cmd: mkhomedir_helper

scheduling:
userScheduler:
enabled: false

singleuser:
defaultUrl: “/lab”

By default on Z2JH the authenticator only controls access to JupyterHub. Since singleuser servers are run in pods they can use the container’s default user jovyan.

Since it is necessary to interact from juputerhub with other tools, it is necessary that the requests be made from an active directory user and the security groups inherited from the directory (The above because everything is under kerberos).

I need to configure something similar to this:

I just don’t know how to do it, since when following the steps, I get a spawner error when the web interface is displayed

Based on the configuration you’ve included in your first post you’re missing: