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

Mechanism names in 'or, 'and', 'eq' or 'if' predicates are not parsed correctly in mechanism selector in Elytron client

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.DR19
    • 7.1.0.DR18
    • Security
    • None

    Description

      When Elytron client configuration file includes sasl-mechanism-selector with string which contains 'or, 'and', 'eq' and 'if' predicate then its values are not parsed correctly. It seems that name of mechanism is parsed as 'name of mechanism'+'1 another character'.

      For example, following element for selector in Elytron client configuration file:

      ...
<sasl-mechanism-selector selector="(DIGEST-MD5||JBOSS-LOCAL-USER)"/>
...

      is parsed as mechanisms DIGEST-MD5|, JBOSS-LOCAL-USER).

      The same behavior happens also if predicate &&, ==, x ? y : z is used.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11067 FAMILY and HASH selectors in Elytron client are parsed incorrectly

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ELY-1187 Mechanism names in 'or, 'and', 'eq' or 'if' predicates are not parsed correctly in mechanism selector in Elytron client

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-11101 Upgrade WildFly Elytron to 1.1.0.Beta46

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11070 Only the last mechanism selector is used in Elytron client configuration

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              chaowan@redhat.com Chao Wang
              olukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: