[jboss-jira] [JBoss JIRA] (AS7-2500) The CLI no longer shows the ssl attribute of a connector
Rich Raposa (Created) (JIRA)
jira-events at lists.jboss.org
Thu Nov 3 11:44:45 EDT 2011
The CLI no longer shows the ssl attribute of a connector
--------------------------------------------------------
Key: AS7-2500
URL: https://issues.jboss.org/browse/AS7-2500
Project: Application Server 7
Issue Type: Bug
Components: CLI
Reporter: Rich Raposa
Assignee: Alexey Loubyansky
When adding a new connector, tab completion shows ssl as a valid attribute and the following command works:
/subsystem=web/connector=https:add(socket-binding=https,scheme=https,protocol="HTTP/1.1",secure=true,ssl={})
But read-resource does not show ssl anymore:
[standalone at localhost:9999 /] /subsystem=web/connector=https:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"enable-lookups" => false,
"enabled" => true,
"max-post-size" => 2097152,
"max-save-post-size" => 4096,
"protocol" => "HTTP/1.1",
"redirect-port" => 8443,
"scheme" => "https",
"secure" => true,
"socket-binding" => "https",
"virtual-server" => undefined
}
}
Also, there is no way in the CLI to add/modify the attributes of ssl (like the certificate-key-file and password):
[standalone at localhost:9999 /] /subsystem=web/connector=https:write-attribute(name=ssl,value={"password"=>"changeit","certificate-key-file"=>".keystore"})
{
"outcome" => "failed",
"failure-description" => "No known attribute called ssl",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list