You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2018/11/07 20:09:00 UTC
[jira] [Updated] (KNOX-1437) Support for cloud federation provider
[ https://issues.apache.org/jira/browse/KNOX-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Risden updated KNOX-1437:
-------------------------------
Fix Version/s: (was: 1.2.0)
> Support for cloud federation provider
> -------------------------------------
>
> Key: KNOX-1437
> URL: https://issues.apache.org/jira/browse/KNOX-1437
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.2.0
> Reporter: Sandeep More
> Assignee: Sandeep More
> Priority: Major
>
> As part of work for KNOX-1339 Cloud Federation use case, we propose a new federation provider that can be used for topology based federation from one Knox instance to another.
> The new provider would be
> {code:xml}
> <provider>
> <role>federation</role>
> <name>CloudFederationProvider</name>
> <enabled>true</enabled>
> <param>
> <name>cloud.federation.host</name>
> <value>cloud</value>
> </param>
> <param>
> <name>cloud.federation.port</name>
> <value>8443</value>
> </param>
> <param>
> <name>cloud.federation.gateway</name>
> <value>gateway</value>
> </param>
> <param>
> <name>cloud.federation.topology</name>
> <value>sandbox</value>
> </param>
> </provider>
> {code}
> The above provider will be used to form a URL that will be used to talk to the federated Knox instance. This provider will also use HeaderPreAuthFederationDispatch internally as a result the federated Knox instance should be using HeaderPreAuth authentication.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)