-
Bug
-
Resolution: Done
-
Minor
-
2.9.0.Final
-
None
-
-
User Experience
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.
- clones
-
-
- Verified
-
