[LMA] ldap integration (AD)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel Plugins |
Invalid
|
Undecided
|
Unassigned | ||
StackLight |
Confirmed
|
Medium
|
LMA-Toolchain Fuel Plugins |
Bug Description
Hey,
in plugins (i checked version 1.0.0) we have ldap integration but its not working correctly with AD ldap. The groups in AD ldap are schema with membefOf and we always assume that we dont have this attribute in ldap.
To make it working (with AD) we need to uncomment ldap scheme for apache:
in https:/
https:/
comment:
group_search_
group_search_filter = "<%= @ldap_group_
and change
member_of = "cn"
to
member_of = "memberOf"
i think the best will be put all this variable to UI and give user possibility to decide how to configure those options.
Changed in fuel-plugins: | |
status: | New → Invalid |
Changed in lma-toolchain: | |
status: | New → Confirmed |
assignee: | nobody → LMA-Toolchain Fuel Plugins (mos-lma-toolchain) |
Changed in lma-toolchain: | |
importance: | Undecided → Medium |
Thanks for reporting issue.
The bug described here is related to Grafana. This is not Apache which deals with LDAP authz but Grafana directly.
Apache handles LDAP authz for the 2 other plugins elasticsearch- kibana and lma_infra_alerting, are they impacted the same way ?