Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8469

The elytron-domain attribute in messaging subsystem doesn't reference capability

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR12
    • 7.1.0.DR11
    • JMS, Security
    • None

    Description

      The elytron-domain attribute in ActiveMQ server configuration must reference capability "org.wildfly.security.security-domain" to allow value validation and enable auto-completion support in CLI. It's just a STRING value now without validation.

      Currently it's possible to do following:

      [standalone@embedded /] /subsystem=messaging-activemq/server=default:write-attribute(name=elytron-domain, value=NoSuchDomain)
{"outcome" => "success"}

      The behavior should be aligned to Batch subsystem for instance:

      [standalone@embedded /] /subsystem=batch-jberet:write-attribute(name=security-domain,value=NoSuchDomain)
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0369: Required capabilities are not available:
    org.wildfly.security.security-domain.NoSuchDomain; There are no known registration points which can provide this capability.",
    "rolled-back" => true
}

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-8687 Server boot error is confusing If Elytron subsystem is removed and attribute elytron-domain set

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is cloned by

          Bug - A problem which impairs or prevents the functions of the product. WFLY-7947 The elytron-domain attribute in messaging subsystem doesn't reference capability

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: JBEAP

              People

                jmesnil1@redhat.com Jeff Mesnil
                josef.cacek@gmail.com Josef Cacek (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: