[JBoss JIRA] (WFLY-7585) Auto-completion does not work for default-realm of Elytron security-domain in CLI
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7585?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-7585:
-----------------------------------
Priority: Minor (was: Major)
> Auto-completion does not work for default-realm of Elytron security-domain in CLI
> ---------------------------------------------------------------------------------
>
> Key: WFLY-7585
> URL: https://issues.jboss.org/browse/WFLY-7585
> Project: WildFly
> Issue Type: Enhancement
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Minor
> Labels: user_experience
>
> Auto-completion does not work for default-realm of Elytron security-domain in CLI. All attributes of security-domain support auto-completion through {{<TAB>}} button. The only one which does not support it is default-realm. It is probably caused by missing capability-reference.
> Example:
> {code}
> /subsystem=elytron/security-domain=domain:add(default-realm=<TAB>
> {code}
> Does not show any security realms. However:
> {code}
> /subsystem=elytron/security-domain=domain:add(permission-mapper=<TAB>
> {code}
> Shows possible permission mappers.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (ELY-800) Elytron ExternalSaslServerFactory.createSaslServer should return null for unsupported policies
by Josef Cacek (JIRA)
Josef Cacek created ELY-800:
-------------------------------
Summary: Elytron ExternalSaslServerFactory.createSaslServer should return null for unsupported policies
Key: ELY-800
URL: https://issues.jboss.org/browse/ELY-800
Project: WildFly Elytron
Issue Type: Bug
Reporter: Josef Cacek
Assignee: Darran Lofthouse
The {{ExternalSaslServerFactory.createSaslServer(String, String, String, Map<String, ?>, CallbackHandler)}} method returns an instance even for properties, for which {{getMechanismNames()}} returns empty array of names.
The {{ExternalSaslServer}} instances should only be created if the mechanism is supported for given properties (configuration).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7585) Auto-completion does not work for default-realm of Elytron security-domain in CLI
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7585?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-7585:
----------------------------------------
[~brian.stansberry] [~harald.pehl] [~claudius] [~jdenise] Do you have any suggestions for this one?
Technically we could make this attribute a capability reference but it needs to reference one of the security realms referenced from this security domain and not all of them
We could go a complete alternative and just make the first in the list the default, I think I had some objections to that from other feedback but it does make the model easier to validate.
> Auto-completion does not work for default-realm of Elytron security-domain in CLI
> ---------------------------------------------------------------------------------
>
> Key: WFLY-7585
> URL: https://issues.jboss.org/browse/WFLY-7585
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Labels: user_experience
>
> Auto-completion does not work for default-realm of Elytron security-domain in CLI. All attributes of security-domain support auto-completion through {{<TAB>}} button. The only one which does not support it is default-realm. It is probably caused by missing capability-reference.
> Example:
> {code}
> /subsystem=elytron/security-domain=domain:add(default-realm=<TAB>
> {code}
> Does not show any security realms. However:
> {code}
> /subsystem=elytron/security-domain=domain:add(permission-mapper=<TAB>
> {code}
> Shows possible permission mappers.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-1341) Expose IO worker runtime data / statistics
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1341?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-1341:
-------------------------------------
Example of output with current proposed impl in PR https://github.com/wildfly/wildfly-core/pull/1990
{noformat}
[standalone@localhost:9990 /] /subsystem=io/worker=default:read-resource(recursive=true, include-runtime=true)
{
"outcome" => "success",
"result" => {
"core-pool-size" => 4,
"io-thread-count" => 16,
"io-threads" => undefined,
"max-pool-size" => 128,
"queue-size" => 0,
"shutdown-requested" => false,
"stack-size" => 0L,
"task-keepalive" => 60,
"task-max-threads" => undefined,
"server" => {
"/127.0.0.1:8080" => {
"connection-count" => -1,
"connection-limit-high-water-mark" => 2147483647,
"connection-limit-low-water-mark" => 2147483647
},
"/127.0.0.1:8443" => {
"connection-count" => -1,
"connection-limit-high-water-mark" => 2147483647,
"connection-limit-low-water-mark" => 2147483647
}
}
}
}
{noformat}
> Expose IO worker runtime data / statistics
> ------------------------------------------
>
> Key: WFCORE-1341
> URL: https://issues.jboss.org/browse/WFCORE-1341
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Remoting
> Affects Versions: 2.0.7.Final
> Reporter: Brad Maxwell
> Assignee: Tomaz Cerar
>
> The remoting subsystem uses a worker-thread-pool which can be configured such as shown below.
> The runtime thread pool information is not exposed when doing read-resource:
> {code}
> /subsystem=remoting:read-resource(include-runtime=true, recursive=true)
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:remoting:1.1">
> <worker-thread-pool
> read-threads="1"
> task-core-threads="4"
> task-keepalive="60"
> task-limit="16384"
> task-max-threads="16"
> write-threads="1"
> />
> <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
> </subsystem>
> {code}
> In tuning and runtime diagnosis, it would be useful to see the thread pool information such as the current size, queue-size, largest-thread-count, etc similar to the ejb3 subsystem thread pool:
> {code}
> /subsystem=ejb3/thread-pool=default:read-resource(include-runtime=true, recursive=true)
> "result" => {
> "active-count" => 0,
> "completed-task-count" => 0L,
> "current-thread-count" => 0,
> "keepalive-time" => {
> "time" => 100L,
> "unit" => "MILLISECONDS"
> },
> "largest-thread-count" => 0,
> "max-threads" => 10,
> "name" => "default",
> "queue-size" => 0,
> "rejected-count" => 0,
> "task-count" => 0L,
> "thread-factory" => undefined
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7585) Auto-completion does not work for default-realm of Elytron security-domain in CLI
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7585?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7585:
----------------------------------
This autocomplete cannot be done using capability-reference, as it does not reference the capability.
It reference one of items from "realms" attribute, which is passed in together with "default-realm" attribute.
This would have to be a bit hacky - it would have to use rest of currently writing CLI command. (And it wouldnt work if the default-realm would be written before realms attribute.)
I suggest to close this.
> Auto-completion does not work for default-realm of Elytron security-domain in CLI
> ---------------------------------------------------------------------------------
>
> Key: WFLY-7585
> URL: https://issues.jboss.org/browse/WFLY-7585
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Labels: user_experience
>
> Auto-completion does not work for default-realm of Elytron security-domain in CLI. All attributes of security-domain support auto-completion through {{<TAB>}} button. The only one which does not support it is default-realm. It is probably caused by missing capability-reference.
> Example:
> {code}
> /subsystem=elytron/security-domain=domain:add(default-realm=<TAB>
> {code}
> Does not show any security realms. However:
> {code}
> /subsystem=elytron/security-domain=domain:add(permission-mapper=<TAB>
> {code}
> Shows possible permission mappers.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months