We don¹t have a sample config for LDAP, as the search pattern differs by LDAPs; You may need contact your LDAP Admin to get some detail;
For the ³ldap.service.*² settings, you can ignore I think; We leave it there because in our deployment we need authenticate service accounts (for system integrations); In our LDAP the service accounts are in a different directory so we need add it; In most of the scenarios, just configure ³ldap.user.*² is good enough; After switch to LDAP, you may need configure group for Kylin admins in LDAP, and then update the ³acl.adminRole² accordingly in kylin.properties, for example: acl.adminRole=ROLE_KYLIN-ADMIN acl.defaultRole=ROLE_ANALYST,ROLE_MODELER These configurations are parsed in kylniSecurity.xml, you can get started from it: https://github.com/KylinOLAP/Kylin/blob/master/server/src/main/resources/ky linSecurity.xml#L72 On 3/17/15, 3:30 PM, "Marek Wiewiorka" <[email protected]> wrote: >ldap.user.groupSearchBase
