[jboss-jira] [JBoss JIRA] (AS7-2500) The CLI no longer shows the ssl attribute of a connector
Alexey Loubyansky (Commented) (JIRA)
jira-events at lists.jboss.org
Thu Nov 3 12:30:46 EDT 2011
[ https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639767#comment-12639767 ]
Alexey Loubyansky commented on AS7-2500:
----------------------------------------
AFAICS, ssl is not an attribute but a child of the connector
[standalone at localhost:9999 /] /subsystem=web/connector=https:read-resource-description
{
"outcome" => "success",
"result" => {
"head-comment-allowed" => true,
"tail-comment-allowed" => true,
"description" => "A web connector.",
"attributes" => {
"name" => {
"type" => STRING,
"description" => "A unique name for the connector.",
"required" => false,
"nillable" => false,
"access-type" => "read-only",
"storage" => "configuration"
},
"protocol" => {
"type" => STRING,
"description" => "The web connector protocol.",
"required" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"socket-binding" => {
"type" => STRING,
"description" => "The web connector socket-binding reference, this connector should be bound to.",
"required" => true,
"nillable" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"scheme" => {
"type" => STRING,
"description" => "The web connector scheme.",
"required" => false,
"default" => "http",
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"executor" => {
"type" => STRING,
"description" => "The name of the executor that should be used for the processing threads of this connector. If undefined defaults to using an internal pool.",
"required" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"enabled" => {
"type" => BOOLEAN,
"description" => "Defines whether the connector should be started on startup.",
"required" => false,
"default" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"enable-lookups" => {
"type" => BOOLEAN,
"description" => "Enable DNS lookups for Servlet API.",
"required" => false,
"default" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"proxy-name" => {
"type" => STRING,
"description" => "The host name that will be used when sending a redirect. The default value is null.",
"required" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"proxy-port" => {
"type" => INT,
"description" => "The port that will be used when sending a redirect.",
"required" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"max-post-size" => {
"type" => INT,
"description" => "Maximum size in bytes of a POST request that can be parsed by the container.",
"required" => false,
"default" => 2097152,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"max-save-post-size" => {
"type" => INT,
"description" => "Maximum size in bytes of a POST request that will be saved during certain authentication schemes.",
"required" => false,
"default" => 4096,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"secure" => {
"type" => BOOLEAN,
"description" => "Indicates if content sent or recieved by the connector is secured from the user perspective.",
"required" => false,
"default" => false,
"access-type" => "read-only",
"storage" => "configuration"
},
"redirect-port" => {
"type" => INT,
"description" => "The port for redirection to a secure connector.",
"required" => false,
"default" => 8443,
"access-type" => "read-only",
"storage" => "configuration"
},
"max-connections" => {
"type" => INT,
"description" => "Amount of concurrent connections that can be processed by the connector with optimum performance. The default value depends on the connector used.",
"required" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"virtual-server" => {
"type" => LIST,
"value-type" => STRING,
"description" => "The list of virtual servers that can be accessed through this connector. The default is to allow all virtual servers.",
"required" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"bytesSent" => {
"type" => INT,
"description" => "\"Number of byte sent by the connector.",
"access-type" => "metric",
"storage" => "runtime"
},
"bytesReceived" => {
"type" => INT,
"description" => "Number of byte received by the connector (POST data).",
"access-type" => "metric",
"storage" => "runtime"
},
"processingTime" => {
"type" => INT,
"description" => "Processing time used by the connector. Im milli-seconds.",
"access-type" => "metric",
"storage" => "runtime"
},
"errorCount" => {
"type" => INT,
"description" => "Number of error that occurs when processing requests by the connector.",
"access-type" => "metric",
"storage" => "runtime"
},
"maxTime" => {
"type" => INT,
"description" => "Max time spent to process a requests.",
"access-type" => "metric",
"storage" => "runtime"
},
"requestCount" => {
"type" => INT,
"description" => "Number of the request processed by the connector.",
"access-type" => "metric",
"storage" => "runtime"
}
},
"children" => {"ssl" => {
"description" => "The SSL configuration of the connector.",
"model-description" => {}
}}
}
}
> 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: Domain Management, Web
> Reporter: Rich Raposa
> Assignee: Jean-Frederic Clere
>
> 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