Security

LDAP Authentication, single group with multiple strategies.

JDukeSplunk
Builder

My gut and Googling tells me this won't work, but I'd like some backup or a link to direct documentation showing why/why-not.

Is it possible to have Splunk connected to LDAP1, LDAP2, and LDAP3 but only have roles mapped to LDAP1 Groups with user accounts from LDAP2 and LDAP3 present in them. This is a MS Active Directory setup, and of course this works for MS authentication because of trusts.

We have the 3 LDAP strategies currently but each has its own set of Splunk groups for role mappings. The AD folks want to consolidate these down to one set in one domain and add users from the other domains to them.

We have added test users, and Splunk can read the group membership but not as names. They show up as ;

CN=S-1-5-21-448539723-1935655697-839522115-47432,CN=ForeignSecurityPrincipals,DC=COMPANYNAME,DC=com
CN=S-1-5-21-448539723-1935655697-839522115-59596,CN=ForeignSecurityPrincipals,DC=COMPANYNAME,DC=com

0 Karma

corey_dick
Path Finder

You're seeing the same issue as this other user (https://answers.splunk.com/answers/2230/ldap-authentication-users-from-another-trusted-domain.html). It seems that the issue has to do with the way that AD responds back to the query. I'm having a similar issue as the linked problem.

0 Karma
Get Updates on the Splunk Community!

Now Available: Cisco Talos Threat Intelligence Integrations for Splunk Security Cloud ...

At .conf24, we shared that we were in the process of integrating Cisco Talos threat intelligence into Splunk ...

Preparing your Splunk Environment for OpenSSL3

The Splunk platform will transition to OpenSSL version 3 in a future release. Actions are required to prepare ...

Easily Improve Agent Saturation with the Splunk Add-on for OpenTelemetry Collector

Agent Saturation What and Whys In application performance monitoring, saturation is defined as the total load ...