[jboss-jira] [JBoss JIRA] (WFCORE-873) Resource alias operation inconsistencies

[Kabir Khan (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100113#comment-13100113 ] 

Kabir Khan commented on WFCORE-873:
-----------------------------------

While reproducing with a test, and double-checking the CLI output, I also notice that there are two levels of result/outcome when using wildcards:
{code}
[standalone at localhost:9990 /] /subsystem=infinispan/cache-container=*/invalidation-cache=*/eviction=EVICTION:read-resource-description
{
    "outcome" => "success",
    "result" => [{
        "address" => [
            ("subsystem" => "infinispan"),
            ("cache-container" => "*"),
            ("invalidation-cache" => "*"),
            ("component" => "eviction")
        ],
        "outcome" => "success",
        "result" => {
            "description" => "The cache eviction configuration.",
             ...
            },
            "operations" => undefined,
            "notifications" => undefined,
            "children" => {}
        }
    }]
}
{code}
vs only one when using the non-wildcard address:
{code}
[standalone at localhost:9990 /] /subsystem=infinispan/cache-container=hibernate/invalidation-cache=entity/eviction=EVICTION:read-resource-description
{
    "outcome" => "success",
    "result" => {
        "description" => "The cache eviction configuration.",
        "attributes" => {
          ...
        },
        "operations" => undefined,
        "notifications" => undefined,
        "children" => {}
    }
}

{code}
I presume that is happening for a reason and will not touch that, since it sounds like the console is depending on this 'double' level when wildcard resources are used.

> Resource alias operation inconsistencies
> ----------------------------------------
>
>                 Key: WFCORE-873
>                 URL: https://issues.jboss.org/browse/WFCORE-873
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Kabir Khan
>            Priority: Critical
>             Fix For: 2.0.0.Beta3
>
>
> Formlery we could request the ../eviction=EVICTION resource. I assume that with the resource name change a transformer kicks that redirects the request to the ../component" => "eviction resource. The response header however contains the wrong address, which prevents clients to correlate the request with the response. 
> *In HAL this breaks the access control mechanism.*
> {noformat}
> [domain at localhost:9990 /] /profile=full/subsystem=infinispan/cache-container=*/invalidation-cache=*/eviction=EVICTION:read-resource-description
> {
>     "outcome" => "success",
>     "result" => [{
>         "address" => [
>             ("profile" => "full"),
>             ("subsystem" => "infinispan"),
>             ("cache-container" => "*"),
>             ("invalidation-cache" => "*"),
>             ("component" => "eviction")
>         ],
>         "outcome" => "success",
>  [...]
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)