[
https://issues.apache.org/jira/browse/KNOX-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915294#comment-16915294
]
ASF subversion and git services commented on KNOX-1934:
-------------------------------------------------------
Commit 9ae8d4e85c84ab6167a9c92d25006c46111babb3 in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=9ae8d4e ]
KNOX-1934 - Setting the default value of knoxsso.cookie.secure.only based on
ssl.enabled flag in gateway-site.xml (#134)
> Setting value of knoxsso.cookie.secure.only based on ssl.enabled in
> gateway.site
> --------------------------------------------------------------------------------
>
> Key: KNOX-1934
> URL: https://issues.apache.org/jira/browse/KNOX-1934
> Project: Apache Knox
> Issue Type: Improvement
> Components: KnoxSSO, Server
> Reporter: Abhishek Shukla
> Assignee: Sandor Molnar
> Priority: Minor
> Fix For: 1.4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, knoxsso.cookie.secure.only is set to true always in knoxsso
> topology, since Knox Gateway is always deployed in SSL enabled mode.
> But if deployment is done with ssl.disabled=true mode, then we can access the
> ADMIN UI only after setting the value for knoxsso.cookie.secure.only = false
> manually.
>
> It will be good to set the knoxsso.cookie.secure.only flag based on
> ssl.disabled flag present in gateway-site configs.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
