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

dir-contexts referral-mode attribute upper/lower case discrepancy

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Minor
    • None
    • 7.3.0.GA, 7.4.0.CD19, 7.3.2.GA
    • Security
    • None
    • False
    • False
    • Undefined
    • Hide
      1. unzip server and start it ./bin/standalone.sh
      2. connect to CLI, define dummy dir-context in elytron subsystem:
        /subsystem=elytron/dir-context=foo:add(url="file:///tmp")
        
      3. list newly added dir-context and see that default value of referral-mode attribute is printed in upper-case:
        /] ls /subsystem=elytron/dir-context=foo
        authentication-context=undefined  connection-timeout=undefined      enable-connection-pooling=false   principal=undefined               read-timeout=undefined            ssl-context=undefined             
        authentication-level=simple       credential-reference=undefined    module=undefined                  properties=undefined              referral-mode=IGNORE              url=file:///tmp
        
      4. write custom value to the attribute and list again:
        /] /subsystem=elytron/dir-context=foo:write-attribute(name=referral-mode,value=THROW)
        /] reload
        /] ls /subsystem=elytron/dir-context=foo
        authentication-context=undefined  connection-timeout=undefined      enable-connection-pooling=false   principal=undefined               read-timeout=undefined            ssl-context=undefined             
        authentication-level=simple       credential-reference=undefined    module=undefined                  properties=undefined              referral-mode=follow              url=file:///tmp
        
      5. referral-mode attribute value is now printed in lower-case
      Show
      unzip server and start it ./bin/standalone.sh connect to CLI, define dummy dir-context in elytron subsystem: /subsystem=elytron/dir-context=foo:add(url= "file: ///tmp" ) list newly added dir-context and see that default value of referral-mode attribute is printed in upper-case: /] ls /subsystem=elytron/dir-context=foo authentication-context=undefined connection-timeout=undefined enable-connection-pooling= false principal=undefined read-timeout=undefined ssl-context=undefined authentication-level=simple credential-reference=undefined module=undefined properties=undefined referral-mode=IGNORE url=file: ///tmp write custom value to the attribute and list again: /] /subsystem=elytron/dir-context=foo:write-attribute(name=referral-mode,value=THROW) /] reload /] ls /subsystem=elytron/dir-context=foo authentication-context=undefined connection-timeout=undefined enable-connection-pooling= false principal=undefined read-timeout=undefined ssl-context=undefined authentication-level=simple credential-reference=undefined module=undefined properties=undefined referral-mode=follow url=file: ///tmp referral-mode attribute value is now printed in lower-case

    Description

      There seems to be a discrepancy of the '/elytron/dir-context[referral-mode]' attribute represented value.

      When there is no value set (default is applied), then particular value is printed in upper-case - IGNORE. Although, when we set custom value, then when we try to read it, it is printed in lower-case now, e.g. ignore (lower-case is also saved in raw xml configuration).

      This behavior started with JBoss EAP 7.3.0.GA and is still present in JBoss EAP 7.4.0.CD19. Not sure whether this change was intentional. I was able to find only this issue which may be kind of related WFCORE-3971.

      In JBoss EAP 7.2.x there was always upper-case value printed.

      What is the issue here:

      1. If this change was NOT intentional -> consider whether we would like to go to original behavior (upper-case returned always, including raw xml)
      2. If this change was intentional -> we should probably update so that even default value is lower-case as otherwise this behavior can be confusing for the customer - sometimes there is printed value in upper-case only, otherwise lower-case only. Also, this may be complication for customer automation scripts too.

      Attachments

        Issue Links

          Activity

            People

              rhn-support-rmartinc Ricardo Martin Camarero
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: