Fwd: LDAP Nested OU support

[Jeffrey Rodriguez <je...@gmail.com>]

Hi folks,
     Wanted to confirm the followin:
"Knox Gateway provides HTTP BASIC authentication against an LDAP user
directory. It currently supports only a single Organizational Unit (OU) and
does not support nested OUs."

if this is true? If so what would it take to support Nested OU? Is this a
limitation of Shiro Provider?

It is very common for enterprises to organize their LDAP directory by
nested OUs.

I can open a Jira, and investigate a solution to contribute to the
community.

Thanks,
                      Jeff Rodriguez

Re: LDAP Nested OU support

[Kevin Minder <ke...@hortonworks.com>]

Hi Jeff,
We are very interested in adding support for this.  It would help greatly if we could get to more concrete examples of how more enterprises organize their LDAP directories.  The challenge here is an efficient implementation that works for most common use cases.
Kevin.

From: Jeffrey Rodriguez <je...@gmail.com>>
Reply-To: "user@knox.apache.org<ma...@knox.apache.org>" <us...@knox.apache.org>>
Date: Tuesday, April 28, 2015 at 11:06 PM
To: "user@knox.apache.org<ma...@knox.apache.org>" <us...@knox.apache.org>>
Subject: Fwd: LDAP Nested OU support


Hi folks,
     Wanted to confirm the followin:
"Knox Gateway provides HTTP BASIC authentication against an LDAP user directory. It currently supports only a single Organizational Unit (OU) and does not support nested OUs."

if this is true? If so what would it take to support Nested OU? Is this a limitation of Shiro Provider?

It is very common for enterprises to organize their LDAP directory by nested OUs.

I can open a Jira, and investigate a solution to contribute to the community.

Thanks,
                      Jeff Rodriguez