Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
LDAP integration is not populating Group Member data in sys_user_grmember table - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • LDAP integration is not populating Group Member data in sys_user_grmember table
KB0687680

LDAP integration is not populating Group Member data in sys_user_grmember table


4987 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

 

LDAP integration is not populating Group Member data in sys_user_grmember table


Problem


We have already imported users and group via LDAP successfully. But the problem is, Group members are not getting populated in sys_user_grmember table.

 

Cause


 In LDAP integration, populating Group Members are handled via an onAfter Transform script which includes below code:

ldapUtils.addMembers(source, target);

The source object in above code refers to import set table which holds the LDAP Group import data. Field u_member in import set table holds Group Member(s) data. Behind the scene, platform use u_member field value in order to find the right match in sys_user table. When the match is found, that particular user is added as a member in sys_user_grmember table.

Most of the time, we found that u_member field field length/size for import set table in dictionary is short therefore, incoming data from the LDAP is truncated which in turn causing no match in sys_user table and this issue appears.

 

Solution


Increase the field size of u_member field in sys_dictionary for the specific import set table and the issue is fixed.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.