[
https://issues.apache.org/jira/browse/KNOX-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-2693:
--------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> When topology is updated twice consecutively with 275ms delay then redeployed
> topology doesnt have 2nd updates
> --------------------------------------------------------------------------------------------------------------
>
> Key: KNOX-2693
> URL: https://issues.apache.org/jira/browse/KNOX-2693
> Project: Apache Knox
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: J.Andreina
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *ENV:*
> Have a custom topology_1.xml with below provider
> {noformat}
> <provider>
> <role>authorization</role>
> <name>CompositeAuthz</name>
> <enabled>true</enabled>
> <param>
> <name>AclsAuthz.atlas-api.acl</name>
> <value>user1;group1;10.10.10.10</value>
> </param>
> </provider>{noformat}
> *Steps:*
> 1. Replace acl "user1" value to "guest" using sed
> sed -i -e 's#user1#guest#g' topology_1.xml
> 2. Within 250 ms issue another sed command to replace acl "group1" value to
> "analyst"
> sed -i -e 's#group1#analyst#g' topology_1.xml
> *{color:red}Issue:{color}*
> After 5 mins redeployed topology_1.xml still have "group1" as acl value
> instead of having analyst.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)