[jboss-jira] [JBoss JIRA] (WFLY-5012) Recent infinispan model changes break client compatibility

[Heiko Braun (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Heiko Braun updated WFLY-5012:
------------------------------
    Description: 
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}

  was:
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}



> Recent infinispan model changes break client compatibility
> ----------------------------------------------------------
>
>                 Key: WFLY-5012
>                 URL: https://issues.jboss.org/browse/WFLY-5012
>             Project: WildFly
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Heiko Braun
>            Assignee: Brian Stansberry
>            Priority: Blocker
>
> 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)