[AMBARI-24913] Update ldap-configuration category in Ambari Configurations data to contain properties to aid in automated LDAP configuration

• Type: Task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.8.0
• Component/s: ambari-server, security
• Labels: pull-request-available
• Assignee: Sandor Molnar
• Reporter: Sandor Molnar
• Created: 16/Nov/18 12:55
• Updated: 26/Feb/19 17:51
• Resolved: 20/Nov/18 09:33

Description

Update ldap-configuration category in Ambari Configurations data to contain properties to aid in automated LDAP configuration:

• ambari.ldap.manage_services
  • This property is used to indicate whether Ambari is to manage relevant services' LDAP configurations or not ("true" | "false")
• ambari.ldap.enabled_services
  • This property is used to declare what services are expected to be configured for LDAP and is expected to be a comma-delimited list of services or "*" to indicate all services.

Examples:

All services

"ambari.ldap.manage_services":"true",
"ambari.ldap.enabled_services":"*"

Only Ranger

"ambari.ldap.manage_services":"true",
"ambari.ldap.enabled_services":"Ranger"

Ranger, and Atlas

"ambari.ldap.manage_services":"true",
"ambari.ldap.enabled_services":"Ranger, Atlas"

Do not manage services

"ambari.ldap.manage_services":"false",
"ambari.ldap.enabled_services":""

Each service in the set of services should have indicated it supports LDAP (see BUG-114409) else it will silently be ignored.

This value should be set via Ambari's REST API or a Blueprint.

Upon setting this value via the Ambari REST API, it is expected that internal logic will be triggered to ensure the relevant services in the list are configured for LDAP or not configured for LDAP as the case may be.
 

Issue Links

• links to: GitHub Pull Request #2629