[jboss-jira] [JBoss JIRA] (AS7-2500) The CLI no longer shows the ssl attribute of a connector

[Rich Raposa (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639779#comment-12639779 ] 

Rich Raposa commented on AS7-2500:
----------------------------------

In the schema, ssl is a child. In the DMR, ssl is an attribute of connector. Either way, there is no CLI command that allows you to edit the ssl settings, which is inconsistent with the :add operation. For example, the following CLI command works:

/subsystem=web/connector=https:add(socket-binding=https,scheme=https,protocol="HTTP/1.1",secure=true,ssl={"password"=>"changeit","certificate-key-file"=>".keystore"})

I've tested it, and the certificate is loaded and everything works great. However, there is no way in the CLI to view your ssl settings, and I can't figure out how to modify them either. In my :add operation above, ssl is an attribue, so for consistency, :write-attribute(name="ssl",value="...") should work, or give me an error message saying the attribute is not writeable. 

There is also an inconsistency in the documentation, which shows the ssl attribute in the :read-resource operation. But I am using a nightly build from two days ago, so something could have easily changed since these docs were written:
https://docs.jboss.org/author/display/AS7/HTTPS+Connectors

                
> 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