[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Fix Version/s: (was: 5.17.5) (was: 5.18.3) > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Major > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Fix Version/s: 5.18.3 (was: 5.18.2) > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.17.5, 5.18.3 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich updated AMQ-9200: Fix Version/s: 5.18.2 (was: 5.18.1) > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.17.5, 5.18.2 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Fix Version/s: 5.18.1 (was: 5.18.0) > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.17.5, 5.18.1 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Priority: Major (was: Blocker) > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.4 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Fix Version/s: 5.17.5 (was: 5.17.4) > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.5 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Priority: Blocker (was: Major) > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 5.18.0, 5.17.4 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Component/s: Broker > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 5.18.0, 5.17.4 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated AMQ-9200: -- Fix Version/s: 5.18.0 5.17.4 > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug >Reporter: Yury Gubernatorov >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 5.18.0, 5.17.4 > > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (AMQ-9200) Multiple plugins elements are allowed by config schema but are not supported
[ https://issues.apache.org/jira/browse/AMQ-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Gubernatorov updated AMQ-9200: --- Description: Configuration schema (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for instance) allows multiple "plugins" elements: But only the last element is taken into account. So if user by mistake ends up with multiple plugins elements in their config it can come as surprise to them that plugins were not configured properly. This can become critical for some users as, for example, authorization comes as a plugin and user does not know if it is working or not unless they perform a negative test. I recently saw real-life configs looking like this: ... ... ... The broker would run, but authorization plugin will not work allowing anyone with the network access to connect without providing credentials. Persistency is not forced as well. We should set maxOccurs="1" on the plugins element probably. was: Configuration schema (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for instance) allows multiple "plugins" elements: But only the last element is taken into account. So if user by mistake ends up with multiple plugins elements in their config it can be a bit of surprise. This can become critical for some users as, for example, authorization comes as a plugin and used does not know if it is working or not unless they do a negative test. I recently saw real-life configs looking like this: ... ... ... The broker would run, but authorization plugin will not work allowing anyone with the network access to connect without providing credentials. Persistency is not ensured as well. We should set maxOccurs="1" on the plugins element probably. > Multiple plugins elements are allowed by config schema but are not supported > > > Key: AMQ-9200 > URL: https://issues.apache.org/jira/browse/AMQ-9200 > Project: ActiveMQ > Issue Type: Bug >Reporter: Yury Gubernatorov >Priority: Major > > Configuration schema > (http://activemq.apache.org/schema/core/activemq-core-5.17.2.xsd for > instance) allows multiple "plugins" elements: > > But only the last element is taken into account. > So if user by mistake ends up with multiple plugins elements in their config > it can come as surprise to them that plugins were not configured properly. > This can become critical for some users as, for example, authorization comes > as a plugin and user does not know if it is working or not unless they > perform a negative test. > I recently saw real-life configs looking like this: > > ... > > ... > > > ... > > > The broker would run, but authorization plugin will not work allowing anyone > with the network access to connect without providing credentials. Persistency > is not forced as well. > We should set maxOccurs="1" on the plugins element probably. -- This message was sent by Atlassian Jira (v8.20.10#820010)
