All Apps and Add-ons

LDAPsearch is not showing latest group membership

jdunlea
Contributor

I have recently added a user to a group.

When I query the user's AD object using ldapsearch, I can see his group membership, however the new group that he was added to is nowhere to be seen.

What is the issue here? Is there some sort of AD cache that the ldapsearch command is querying and the new group membership change has not been updated in the cache? (Or something like that)

0 Karma
1 Solution

jdunlea
Contributor

Turns out the problem was the type of group that I was looking at. It was a global group and not a universal group in AD and hence it was not propagating across all of the domains.

Once I changed the group type it worked perfectly.

Thanks for the help!

View solution in original post

0 Karma

jdunlea
Contributor

Turns out the problem was the type of group that I was looking at. It was a global group and not a universal group in AD and hence it was not propagating across all of the domains.

Once I changed the group type it worked perfectly.

Thanks for the help!

0 Karma

nnmiller
Contributor

Have you verified that AD is properly replicating?

Try using an AD account with admin privileges to do the ldapsearch command. If that account can see the members, then the generic ldap query user does not have the proper permissions to read the AD objects; you will have to add read group membership (at a minimum) to the generic ldap query user's permissions.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

Splunk is officially part of Cisco

Revolutionizing how our customers build resilience across their entire digital footprint.   Splunk ...

Splunk APM & RUM | Planned Maintenance March 26 - March 28, 2024

There will be planned maintenance for Splunk APM and RUM between March 26, 2024 and March 28, 2024 as ...