[
https://issues.apache.org/jira/browse/KNOX-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McCay updated KNOX-1314:
------------------------------
Description:
In most instances, the use of the SSOCookieProvider in a topology is likely
colocated with the topology that is hosting the KnoxSSO service endpoint. We
can provide a default providerUrl that is based on the hostname, port of the
incoming request along with the wellknown knoxsso topology.
When there is a different URL needed then the current configuration will be
used to override this default.
This will allow us to be able to use the SSOCookieProvider out of the box for
topologies like manager.xml where we host the Knox Admin UI.
It will need to also accommodate X-Forwarded headers in order to account for
when Knox is itself being proxied.
was:
In most instances, the use of the SSOCookieProvider in a topology is likely
colocated with the topology that is hosting the KnoxSSO service endpoint. We
can provide a default providerUrl that is based on the hostname, port of the
incoming request along with the wellknown knoxsso topology.
When there is a different URL needed then the current configuration will be
used to override this default.
This will allow us to be able to use the SSOCookieProvider out of the box for
topologies like manager.xml where we host the Knox Admin UI.
> SSOCookieProvider should be able to derive a default provider URL
> -----------------------------------------------------------------
>
> Key: KNOX-1314
> URL: https://issues.apache.org/jira/browse/KNOX-1314
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 1.1.0
>
>
> In most instances, the use of the SSOCookieProvider in a topology is likely
> colocated with the topology that is hosting the KnoxSSO service endpoint. We
> can provide a default providerUrl that is based on the hostname, port of the
> incoming request along with the wellknown knoxsso topology.
> When there is a different URL needed then the current configuration will be
> used to override this default.
> This will allow us to be able to use the SSOCookieProvider out of the box for
> topologies like manager.xml where we host the Knox Admin UI.
> It will need to also accommodate X-Forwarded headers in order to account for
> when Knox is itself being proxied.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
