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
SplunkTrust
SplunkTrust

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!

Observe and Secure All Apps with Splunk

  Join Us for Our Next Tech Talk: Observe and Secure All Apps with SplunkAs organizations continue to innovate ...

Splunk Decoded: Business Transactions vs Business IQ

It’s the morning of Black Friday, and your e-commerce site is handling 10x normal traffic. Orders are flowing, ...

Fastest way to demo Observability

I’ve been having a lot of fun learning about Kubernetes and Observability. I set myself an interesting ...