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

Inconsistent credential-reference attribute writing to model through web console

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 7.1.0.DR14
    • 7.1.0.DR11
    • Web Console
    • None
    • User Experience
    • Hide
      1. Start EAP
      2. Configure recent changes monitoring /core-service=management/service=configuration-changes:add(max-history=100)
      3. Write attribute
      4. List changes by /core-service=management/service=configuration-changes:list-changes
      Show
      Start EAP Configure recent changes monitoring /core-service=management/service=configuration-changes:add(max-history=100) Write attribute List changes by /core-service=management/service=configuration-changes:list-changes

      When setting credential reference attributes in web console it is not propagated to model consistently. This is how it is written in JMS bridge (notice the explicit definition of undefined attributes):

      {
                  "operation-date" => "2017-02-13T10:45:48.149Z",
                  "access-mechanism" => "HTTP",
                  "remote-address" => "/127.0.0.1",
                  "outcome" => "success",
                  "operations" => [{
                      "operation" => "write-attribute",
                      "address" => [
                          ("subsystem" => "messaging-activemq"),
                          ("jms-bridge" => "fooJMSBridge")
                      ],
                      "name" => "source-credential-reference",
                      "value" => {
                          "alias" => undefined,
                          "clear-text" => "foobar",
                          "store" => undefined,
                          "type" => undefined
                      },
                      "operation-headers" => {
                          "access-mechanism" => "HTTP",
                          "caller-type" => "user"
                      }
                  }]
              }
      

      And this is how it is saved in native bridge setting - no undefined values are written:

      {
                  "operation-date" => "2017-02-13T10:41:00.983Z",
                  "access-mechanism" => "HTTP",
                  "remote-address" => "/127.0.0.1",
                  "outcome" => "success",
                  "operations" => [{
                      "address" => [
                          ("subsystem" => "messaging-activemq"),
                          ("server" => "default"),
                          ("bridge" => "foobar")
                      ],
                      "operation" => "write-attribute",
                      "name" => "credential-reference",
                      "value" => {"clear-text" => "foobar"},
                      "operation-headers" => {
                          "access-mechanism" => "HTTP",
                          "caller-type" => "user"
                      }
                  }]
              }
      

      This behavior could confuse user.

      Suggestion for improvement: Make writing of these attributes consistent by not defining explicit undefined values.

            mstefank Martin Stefanko
            jkasik@redhat.com Jan Kašík
            Jan Kašík Jan Kašík
            Jan Kašík Jan Kašík
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: