[ 
https://issues.apache.org/jira/browse/KNOX-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sandor Molnar updated KNOX-1299:
--------------------------------

+Apache Knox 3.0.0 release preparation+
   
We are about to cut the 3.0.0 release branch. master will move on to 3.1.0.
This issue is currently unresolved and is not automatically included in 3.0.0. 
Please choose one of the following:
# If this belongs in 3.0.0: once the branch is cut, cherry-pick your commit(s) 
onto the new v3.0.0 branch in addition to master. Leave Fix Version = 3.0.0 so 
we can track it.
# Do nothing: we will move this issue to the next release (3.1.0) as part of 
release cleanup.
   
If we don't hear back and see no cherry-pick, the issue will be re-targeted to 
3.1.0. Thanks!

> Admin API does not serialize older deployed topology file with 
> identity-assertion provider
> ------------------------------------------------------------------------------------------
>
>                 Key: KNOX-1299
>                 URL: https://issues.apache.org/jira/browse/KNOX-1299
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: AdminUI
>    Affects Versions: 0.14.0
>            Reporter: J.Andreina
>            Priority: Critical
>             Fix For: 3.0.0
>
>
> Step 1: Create a shared provider file from admin-UI "descriptor1" with only 
> one provider "hostmap"
> Step 2: Create a descriptor file "file1" pointing to "descriptor1" with any 
> one service
>     Deployed topology "file1.xml" will have 2 providers when viewed from 
> admin-ui "hostmap" and "identity-assertion"
> Step 3: Create a shared provider file from admin-UI "descriptor2" with only 
> one provider "hostmap"
> Step 4: Create a descriptor file "file2" pointing to "descriptor2" with any 
> one service
> Expected:
> Both file1.xml and file2.xml generated topology should have 2 descriptors 
> "hostmap" and "identity-assertion"
> Issue:
> file1.xml doesnt have "identity-assertion" provider when viewed from admin-ui



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to