[
https://issues.apache.org/jira/browse/AMBARI-16021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Nettleton updated AMBARI-16021:
--------------------------------------
Status: Patch Available (was: In Progress)
> Update LogSearch integration to use configuration to obtain credential
> ----------------------------------------------------------------------
>
> Key: AMBARI-16021
> URL: https://issues.apache.org/jira/browse/AMBARI-16021
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16021.patch
>
>
> The LogSearch integration components in Ambari needs to obtain the credential
> used to connect to the LogSearch service via a configuration mechanism.
> In the initial checkins, the integration code used a hard-coded credential.
> Now that AMBARI-15884 has implemented the stack and configuration support to
> allow a user to configure the credential for the LogSearch Server, the Ambari
> Integration layer should use this configuration, defined in:
> ambari/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-admin-properties.xml
> This current JIRA tracks the work involved in updating the integration layer
> to obtain the credential from the cluster's configuration, and use this
> credential to connect to the LogSearch service.
> I'm working on a fix for this, and will be submitting a patch shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
