10:44 a.m.
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@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@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
10:48 a.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky updated AS7-2500:
-----------------------------------
Assignee: Brian Stansberry (was: Alexey Loubyansky)
Component/s: Domain Management
Web
(was: CLI)
Again, that's a CLI issue. CLI operations are an interface for the domain management
model. If something can't be done or isn't showing up it's a domain management
issue.
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: Brian Stansberry
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@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@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
11:22 a.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-2500:
-------------------------------------
Assignee: Jean-Frederic Clere (was: Brian Stansberry)
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@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@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
11:30 a.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2500:
----------------------------------------
AFAICS, ssl is not an attribute but a child of the connector
[standalone@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@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@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
11:47 a.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
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@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@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
12:11 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2500:
----------------------------------------
Try navigating into the connector. SSL should be a child.
The model has changed then. And there should be a new way to modify the thing.
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@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@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
12:13 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky edited comment on AS7-2500 at 11/3/11 1:12 PM:
-----------------------------------------------------------------
Again, that's *not* a CLI issue. CLI operations are an interface for the domain
management model. If something can't be done or isn't showing up it's a domain
management issue.
was (Author: aloubyansky):
Again, that's a CLI issue. CLI operations are an interface for the domain
management model. If something can't be done or isn't showing up it's a domain
management issue.
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@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@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
12:13 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Alexey Loubyansky commented on AS7-2500:
----------------------------------------
In DMR it is a child, not an attribute. It's a parameter of 'add' but it
doesn't make it an attribute. See add operation description and resource 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@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@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
12:17 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2500:
------------------------------------------
I have a build using: read-resource(recursive=true)
+++
"ssl" => {"configuration" => {
"key-alias" => "tomcat",
"password" => "changeit"
}}
+++
and:
[standalone@localhost:9999 ssl=configuration] :write-attribute(name=password, value=done)
{"outcome" => "success"}
[standalone@localhost:9999 ssl=configuration] :read-resource
{
"outcome" => "success",
"result" => {
"key-alias" => "tomcat",
"password" => "done"
}
}
It works for me, may be not the way you except it?
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@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@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
12:29 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Rich Raposa commented on AS7-2500:
----------------------------------
Jean-Frederic: the commands you have are exactly what I would expect! But, they do not
work on my build. Like I said, I am running a build from Oct. 31. Are you using one newer
than that? Here is what I get:
[standalone@localhost:9999 ssl=configuration] :write-attribute(name=password, value=done)
Failed to get the list of supported operation properties.
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@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@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
12:55 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Jean-Frederic Clere commented on AS7-2500:
------------------------------------------
you need a today build about 4 hours ago :D
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@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@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
3:30 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2500:
----------------------------------
Fix Version/s: 7.1.0.CR1
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
Fix For: 7.1.0.CR1
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@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@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
2:59 p.m.
[
https://issues.jboss.org/browse/AS7-2500?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-2500.
-----------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Final)
Resolution: Done
Based on the discussion above, it appears whatever the issue was it was fixed sometime in
the CR1 cycle. Please re-open if that is not the case.
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
Fix For: 7.1.0.CR1
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@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@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
4679
days inactive
4755
days old
12 comments
9 participants
participants (9)
-
Alexey Loubyansky (Commented) (JIRA) -
Alexey Loubyansky (Issue Comment Edited) (JIRA)
-
Alexey Loubyansky (Updated) (JIRA)
-
Brian Stansberry (Assigned) (JIRA)
-
Brian Stansberry (JIRA)
-
Brian Stansberry (Updated) (JIRA)
-
Jean-Frederic Clere (Commented) (JIRA)
-
Rich Raposa (Commented) (JIRA)
-
Rich Raposa (Created) (JIRA)