[
https://issues.apache.org/jira/browse/AMBARI-20193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885439#comment-15885439
]
Miklos Gergely commented on AMBARI-20193:
-----------------------------------------
committed to trunk:
{code:java}
commit eb784aaa1f21f98982a405ab2da5f0e659f96102
Author: Miklos Gergely <[email protected]>
Date: Mon Feb 27 10:30:21 2017 +0100
AMBARI-20193 Log Search Portal is not working with HTTPS with it's own
created Key Store (mgergely)
Change-Id: I94555222f16dec59a5be80e273a9fbc25e47ba68
{code}
committed to branch-2.5:
{code:java}
commit d4ce989f079c9ac6dc266117359420671bbce19f
Author: Miklos Gergely <[email protected]>
Date: Mon Feb 27 10:31:31 2017 +0100
AMBARI-20193 Log Search Portal is not working with HTTPS with it's own
created Key Store (mgergely)
Change-Id: I9f4c7097eabb197fb065d1ab7e10d5a0a66036af
{code}
> 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)
