Petals ESB Container

Calling JMXContainerAdministration.getTopology() to get JBI artifacts with an invalid passphrase should fail

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 5.0.2
  • Fix Version/s: 5.1.0
  • Component/s: Administration
  • Security Level: Public
  • Description:
    Hide

    Currently,

    If calling JMXContainerAdministration.getTopology() with an invalid passphrase and retrieveJbiArtifacts to true, then the artifacts are not retrieved for all containers (except the first one for which we have the credentials) and the passphrase failure is silent.

    Basically, the idea is that if I ask for the artifacts, I either want them, or I want the command to fail.
    So instead, an exception should be thrown because of the invalid passphrase.

    The problem is that retrieveJbiArtifacts set to true should imply that TopologyService.retrieveTopology() should be called with isSensibleInformationExpected set to true!

    Show
    Currently, If calling JMXContainerAdministration.getTopology() with an invalid passphrase and retrieveJbiArtifacts to true, then the artifacts are not retrieved for all containers (except the first one for which we have the credentials) and the passphrase failure is silent. Basically, the idea is that if I ask for the artifacts, I either want them, or I want the command to fail. So instead, an exception should be thrown because of the invalid passphrase. The problem is that retrieveJbiArtifacts set to true should imply that TopologyService.retrieveTopology() should be called with isSensibleInformationExpected set to true!
  • Environment:
    -

Activity

Victor NOËL made changes - Fri, 25 Nov 2016 - 13:02:18 +0100
Field Original Value New Value
Summary Calling JMXContainerAdministration.getTopology() with an invalid passphrase and retrieveJbiArtifacts to true shouldn't work Calling JMXContainerAdministration.getTopology() with an invalid passphrase and retrieveJbiArtifacts to true doesn't return the artifacts
Priority Blocker [ 1 ]
Description Currently,

If calling {{JMXContainerAdministration.getTopology()}} with an invalid passphrase and {{retrieveJbiArtifacts}} to {{true}}, then the artifacts are not retrieved for all containers (except the first one for which we have the credentials).

Instead, an exception should be thrown because of the invalid passphrase.

The problem is that {{retrieveJbiArtifacts}} set to {{true}} should imply that {{TopologyService.retrieveTopology()}} should be called with {{isSensibleInformationExpected}} set to {{true}}!
Currently,

If calling {{JMXContainerAdministration.getTopology()}} with an invalid passphrase and {{retrieveJbiArtifacts}} to {{true}}, then the artifacts are not retrieved for all containers (except the first one for which we have the credentials) and the passphrase failure is silent.

Basically, the idea is that if I ask for the artifacts, I either want them, or I want the command to fail.
So instead, an exception should be thrown because of the invalid passphrase.

The problem is that {{retrieveJbiArtifacts}} set to {{true}} should imply that {{TopologyService.retrieveTopology()}} should be called with {{isSensibleInformationExpected}} set to {{true}}!
Victor NOËL made changes - Fri, 25 Nov 2016 - 13:02:29 +0100
Status New [ 10000 ] Open [ 10002 ]
Priority Blocker [ 1 ] Major [ 3 ]
Assignee Christophe DENEUX [ cdeneux ] Victor NOËL [ vnoel ]
Victor NOËL made changes - Fri, 25 Nov 2016 - 13:02:33 +0100
Status Open [ 10002 ] In Progress [ 10003 ]
Victor NOËL made changes - Fri, 25 Nov 2016 - 13:10:29 +0100
Summary Calling JMXContainerAdministration.getTopology() with an invalid passphrase and retrieveJbiArtifacts to true doesn't return the artifacts Calling JMXContainerAdministration.getTopology() to get JBI artifacts with an invalid passphrase should fail
Victor NOËL made changes - Thu, 1 Dec 2016 - 11:07:42 +0100
Fix Version/s 5.1.0 [ 10670 ]
Victor NOËL made changes - Fri, 2 Dec 2016 - 17:34:57 +0100
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]

People

Dates

  • Created:
    Fri, 25 Nov 2016 - 12:41:37 +0100
    Updated:
    Fri, 2 Dec 2016 - 17:34:56 +0100
    Resolved:
    Fri, 2 Dec 2016 - 17:34:56 +0100