We have several AD groups within the root IDM group, is there a way to wildcard those nested groups (IDM-BANNER, IDM-FINAID) and have them authenticate or will indexes need to be created for each nested group?
On Wednesday, November 14, 2018 at 3:14:02 PM UTC-5, Zach Tackett wrote: > > So we need to allow users to login to our LDAP/CAS 5.0 server from their > respective AD groups, there is a root group called "IDM", and within it are > groups called IDM-BANNER, IDM-FINAID, > > I have tried the following: > > cas.authn.ldap[1].dnFormat=cn=%s,ou=IDM,dc=marshall,dc=edu > cas.authn.ldap[1].dnFormat=cn=%s,ou=IDM,ou=IDM-FINAID,dc=marshall,dc=edu > cas.authn.ldap[1].dnFormat=cn=%s,ou=IDM-FINAID,dc=marshall,dc=edu > cas.authn.ldap[1].dnFormat=cn=%s,ou=IDM,ou=IDM-BANNER,dc=marshall,dc=edu > cas.authn.ldap[1].dnFormat=cn=%s,ou=IDM-BANNER,dc=marshall,dc=edu > > None of which are working. Can OU's be grouped/nested within the listing, > does CAS/LDAP not like the nested AD groups? > > > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/a502221e-e62a-4292-828b-e9da684cc3d4%40apereo.org.
