[JBoss JIRA] (WFLY-7582) Wrong resource and operation descriptions for Elytron filesystem-realm in CLI and XSD
by Ondrej Lukas (JIRA)
Ondrej Lukas created WFLY-7582:
----------------------------------
Summary: Wrong resource and operation descriptions for Elytron filesystem-realm in CLI and XSD
Key: WFLY-7582
URL: https://issues.jboss.org/browse/WFLY-7582
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
There are some wrong or insufficient resource and operation description for Elytron filesystem-realm in CLI:
* attribute {{levels}} for filesystem-realm - description says "The number of levels of directory hashing to apply.", but created directory structure does not use any hashing. Example how it works: when levels is set to 3 then for user admin following directory structure and file a/d/m/admin.xml is used. Description of levels should be fixed. This should be also fixed in XSD.
* description of {{digest}} password encryption/hash mechanisms in {{set-password}} operation for identity of filesystem-realm says "A password using a salted digest." which is wrong. It seems it is copy-pasted from {{salted-simple-digest}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7582) Wrong resource and operation descriptions for Elytron filesystem-realm in CLI and XSD
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7582?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7582:
-------------------------------
Affects Version/s: 11.0.0.Alpha1
> Wrong resource and operation descriptions for Elytron filesystem-realm in CLI and XSD
> -------------------------------------------------------------------------------------
>
> Key: WFLY-7582
> URL: https://issues.jboss.org/browse/WFLY-7582
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
>
> There are some wrong or insufficient resource and operation description for Elytron filesystem-realm in CLI:
> * attribute {{levels}} for filesystem-realm - description says "The number of levels of directory hashing to apply.", but created directory structure does not use any hashing. Example how it works: when levels is set to 3 then for user admin following directory structure and file a/d/m/admin.xml is used. Description of levels should be fixed. This should be also fixed in XSD.
> * description of {{digest}} password encryption/hash mechanisms in {{set-password}} operation for identity of filesystem-realm says "A password using a salted digest." which is wrong. It seems it is copy-pasted from {{salted-simple-digest}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1986) Generate a parser from a formal grammer of CLI
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created WFCORE-1986:
--------------------------------------
Summary: Generate a parser from a formal grammer of CLI
Key: WFCORE-1986
URL: https://issues.jboss.org/browse/WFCORE-1986
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Affects Versions: 3.0.0.Alpha12
Reporter: Hisanobu Okuda
Having a formal grammar is a simple and good way to rigorously define things, and using a parser generator instead of writing parser code by hand will result in a reduction in defective edge cases.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Ken Wills commented on WFCORE-1985:
-----------------------------------
I guess the question is, do we want group-name for RRD here, or do we want group-name for RR vs what seems to be currently name? RR is using NameAndGroup, but I think it might be reordering the results into a TreeMap based just on name (I haven't looked at that super closely yet.)
> :read-resource-description operation should consistently order resources by alphabet
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Ken Wills
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1985:
------------------------------------------
Interesting. NameAndGroup has two constructors, one that takes an AttributeDefinition, one that doesn't. The AD one incorporates the group if the AD has one. The constructor with the AD is not used, and only the name is used, if no AD is available. But I don't see why the AD would be available in the r-r-d case and not in the r-r case.
> :read-resource-description operation should consistently order resources by alphabet
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Ken Wills
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Ken Wills edited comment on WFCORE-1985 at 11/14/16 8:26 PM:
-------------------------------------------------------------
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{{
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
etc...
}}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
was (Author: luck3y):
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{{
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
}}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
> :read-resource-description operation should consistently order resources by alphabet
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Ken Wills
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Ken Wills edited comment on WFCORE-1985 at 11/14/16 8:25 PM:
-------------------------------------------------------------
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{{
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
[etc]
}}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
was (Author: luck3y):
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{{test}}
{{
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
{
"outcome" => "success",
"result" => {
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
}
}
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
[etc]
}}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
> :read-resource-description operation should consistently order resources by alphabet
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Ken Wills
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Ken Wills edited comment on WFCORE-1985 at 11/14/16 8:25 PM:
-------------------------------------------------------------
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{{
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
}}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
was (Author: luck3y):
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{{
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
[etc]
}}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
> :read-resource-description operation should consistently order resources by alphabet
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Ken Wills
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Ken Wills edited comment on WFCORE-1985 at 11/14/16 8:24 PM:
-------------------------------------------------------------
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{{
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
{
"outcome" => "success",
"result" => {
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
}
}
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
[etc]
}}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
was (Author: luck3y):
Well, I'm not sure exactly about "consistent" here, so just to be clear:
{quote}
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource()
{
"outcome" => "success",
"result" => {
"add-component-via-interceptor" => true,
"auth-method" => "username_password",
"caller-propagation" => "none",
"client-requires" => "None",
"client-supports" => "MutualAuth",
"confidentiality" => "none",
"detect-misordering" => "none",
"detect-replay" => "none",
"export-corbaloc" => true,
"giop-version" => "1.2",
"high-water-mark" => undefined,
"integrity" => "none",
"number-to-reclaim" => undefined,
"persistent-server-id" => "1",
"properties" => undefined,
"realm" => undefined,
"required" => false,
"root-context" => "JBoss/Naming/root",
"security" => "identity",
"security-domain" => undefined,
"server-requires" => "None",
"server-supports" => "MutualAuth",
"socket-binding" => "iiop",
"ssl-socket-binding" => "iiop-ssl",
"support-ssl" => false,
"transactions" => "spec",
"trust-in-client" => "none",
"trust-in-target" => "none"
}
}
{quote}
{quote}
[standalone@localhost:9990 /] /subsystem=iiop-openjdk:read-resource-description()
(snip for brevity)
"auth-method"
"realm"
"required"
"security"
"transactions"
"export-corbaloc"
"root-context"
"giop-version"
"persistent-server-id"
"socket-binding"
[etc]
{quote}
Perhaps read-resource has an issue with NameAndGroup ordering, if the group-name one is correct?
> :read-resource-description operation should consistently order resources by alphabet
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Ken Wills
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months