When the LDAPListener does not create new users in ServiceNowSummaryLDAPListener does not create new users in ServiceNowInstructions If you make change to an Active Directory/LDAP user (which is also an user in ServiceNow), listener will synchronize this change if the transform map is properly defined. If you make change to an Active Directory/LDAP user (which isn't an user in ServiceNow), listener will skip this change. If you try to log on with this newly created user, even if it is not existed in ServiceNow. ServiceNow will look up in your AD and create this user for you (please search documentation for "On-demand LDAP login") If you don't log on with this newly created user, you need wait manual/scheduled load to create this user for you.If you create a new Active Directory/LDAP user, listener will create an user for you in ServiceNow. Add the properties (sys_properties.list) and set the value to true for glide.ldap.listen.verbose and glide.ldap.debug Request to add a user in LDAP/AD and check the logs to see if the user comes in using the distinguishname of the user who got added.NOTE for LDAP via midserver you have to add the properties in the MIDServer and then restart the midserver. Related LinksEnable an LDAP listener and set system properties The listener can be deployed on a Microsoft Active Directory server that supports persistent queries (ADNotify), or on an LDAP server that supports persistent search request control (with OID 2.16.840.1.113730.3.4.3).