[
https://issues.apache.org/jira/browse/AMBARI-20193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885498#comment-15885498
]
Hudson commented on AMBARI-20193:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6867 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6867/])
AMBARI-20193 Log Search Portal is not working with HTTPS with it's own
(mgergely:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eb784aaa1f21f98982a405ab2da5f0e659f96102])
* (edit) ambari-logsearch/docker/test-config/logsearch/logsearch-env.sh
* (edit) ambari-logsearch/docker/bin/start.sh
* (edit)
ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/util/SSLUtil.java
* (edit) ambari-logsearch/docker/logsearch-docker.sh
> Log Search Portal is not working with HTTPS with it's own created Key Store
> ---------------------------------------------------------------------------
>
> Key: AMBARI-20193
> URL: https://issues.apache.org/jira/browse/AMBARI-20193
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.5.0
> Reporter: Miklos Gergely
> Assignee: Miklos Gergely
> Fix For: 2.5.0
>
> Attachments: AMBARI-20193.patch
>
>
> If "Advanced logsearch-env / Log Search UI Protocol" is set to https and we
> let Log Search to create it's own Key Store than it's not working fine, the
> service starts but the portal is unavailable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)