[JBoss JIRA] (ELY-1244) Fix JwtSecurityRealmTest.testUnsecuredJwt
by Ondrej Kotek (JIRA)
Ondrej Kotek created ELY-1244:
---------------------------------
Summary: Fix JwtSecurityRealmTest.testUnsecuredJwt
Key: ELY-1244
URL: https://issues.jboss.org/browse/ELY-1244
Project: WildFly Elytron
Issue Type: Bug
Components: Testsuite
Affects Versions: 1.1.0.Beta52
Reporter: Ondrej Kotek
Assignee: Ondrej Kotek
{{JwtSecurityRealmTest.testUnsecuredJwt}} should be usable for verification of ELY-1193.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8933) Description of path attributes in messaging subsystem contains HTML tags
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-8933?page=com.atlassian.jira.plugin.... ]
Romain Pelisse commented on WFLY-8933:
--------------------------------------
Adding upstream issue
> Description of path attributes in messaging subsystem contains HTML tags
> ------------------------------------------------------------------------
>
> Key: WFLY-8933
> URL: https://issues.jboss.org/browse/WFLY-8933
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 11.0.0.Alpha1
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Priority: Minor
>
> Description of attributes {{path}} and {{relative-to}} shown in CLI contains HTML tags.
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/path=paging-directory:read-resource-description
> {noformat}
> {panel}
> "paging-directory" => {
> "path" => {
> "description" => "The actual filesystem path. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path. {color:#d04437}<p>{color}If treated as an absolute path, the actual runtime pathname specified by the value of this attribute will be determined as follows: {color:#d04437}</p>{color}If this value is already absolute, then the value is directly used. Otherwise the runtime pathname is resolved in a system-dependent way. On UNIX systems, a relative pathname is made absolute by resolving it against the current user directory. On Microsoft Windows systems, a relative pathname is made absolute by resolving it against the current directory of the drive named by the pathname, if any; if not, it is resolved against the current user directory.",
> },
> "relative-to" => {
> "description" => "The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute. The standard paths provided by the system include:{color:#d04437}<ul><li>{color}jboss.home - the root directory of the JBoss AS distribution{color:#d04437}</li>{color}<li>user.home - user's home directory{color:#d04437}</li><li>{color}user.dir - user's current working directory</li><li>java.home - java installation directory{color:#d04437}</li><li>{color}jboss.server.base.dir - root directory for an individual server instance{color:#d04437}</li><li>{color}jboss.server.data.dir - directory the server will use for persistent data file storage{color:#d04437}</li><li>{color}jboss.server.log.dir - directory the server will use for log file storage{color:#d04437}</li><li>{color}jboss.server.tmp.dir - directory the server will use for temporary file storage{color:#d04437}</li><li>{color}jboss.domain.servers.dir - directory under which a host controller will create the working area for individual server instances{color:#d04437}</li></ul>{color}"
> },
> }
> {panel}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8933) Description of path attributes in messaging subsystem contains HTML tags
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-8933?page=com.atlassian.jira.plugin.... ]
Romain Pelisse updated WFLY-8933:
---------------------------------
Description:
Description of attributes {{path}} and {{relative-to}} shown in CLI contains HTML tags.
{noformat}
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/path=paging-directory:read-resource-description
{noformat}
{panel}
"paging-directory" => {
"path" => {
"description" => "The actual filesystem path. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path. {color:#d04437}<p>{color}If treated as an absolute path, the actual runtime pathname specified by the value of this attribute will be determined as follows: {color:#d04437}</p>{color}If this value is already absolute, then the value is directly used. Otherwise the runtime pathname is resolved in a system-dependent way. On UNIX systems, a relative pathname is made absolute by resolving it against the current user directory. On Microsoft Windows systems, a relative pathname is made absolute by resolving it against the current directory of the drive named by the pathname, if any; if not, it is resolved against the current user directory.",
},
"relative-to" => {
"description" => "The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute. The standard paths provided by the system include:{color:#d04437}<ul><li>{color}jboss.home - the root directory of the JBoss AS distribution{color:#d04437}</li>{color}<li>user.home - user's home directory{color:#d04437}</li><li>{color}user.dir - user's current working directory</li><li>java.home - java installation directory{color:#d04437}</li><li>{color}jboss.server.base.dir - root directory for an individual server instance{color:#d04437}</li><li>{color}jboss.server.data.dir - directory the server will use for persistent data file storage{color:#d04437}</li><li>{color}jboss.server.log.dir - directory the server will use for log file storage{color:#d04437}</li><li>{color}jboss.server.tmp.dir - directory the server will use for temporary file storage{color:#d04437}</li><li>{color}jboss.domain.servers.dir - directory under which a host controller will create the working area for individual server instances{color:#d04437}</li></ul>{color}"
},
}
{panel}
> Description of path attributes in messaging subsystem contains HTML tags
> ------------------------------------------------------------------------
>
> Key: WFLY-8933
> URL: https://issues.jboss.org/browse/WFLY-8933
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 11.0.0.Alpha1
> Reporter: Romain Pelisse
> Assignee: Jeff Mesnil
> Priority: Minor
>
> Description of attributes {{path}} and {{relative-to}} shown in CLI contains HTML tags.
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/path=paging-directory:read-resource-description
> {noformat}
> {panel}
> "paging-directory" => {
> "path" => {
> "description" => "The actual filesystem path. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path. {color:#d04437}<p>{color}If treated as an absolute path, the actual runtime pathname specified by the value of this attribute will be determined as follows: {color:#d04437}</p>{color}If this value is already absolute, then the value is directly used. Otherwise the runtime pathname is resolved in a system-dependent way. On UNIX systems, a relative pathname is made absolute by resolving it against the current user directory. On Microsoft Windows systems, a relative pathname is made absolute by resolving it against the current directory of the drive named by the pathname, if any; if not, it is resolved against the current user directory.",
> },
> "relative-to" => {
> "description" => "The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute. The standard paths provided by the system include:{color:#d04437}<ul><li>{color}jboss.home - the root directory of the JBoss AS distribution{color:#d04437}</li>{color}<li>user.home - user's home directory{color:#d04437}</li><li>{color}user.dir - user's current working directory</li><li>java.home - java installation directory{color:#d04437}</li><li>{color}jboss.server.base.dir - root directory for an individual server instance{color:#d04437}</li><li>{color}jboss.server.data.dir - directory the server will use for persistent data file storage{color:#d04437}</li><li>{color}jboss.server.log.dir - directory the server will use for log file storage{color:#d04437}</li><li>{color}jboss.server.tmp.dir - directory the server will use for temporary file storage{color:#d04437}</li><li>{color}jboss.domain.servers.dir - directory under which a host controller will create the working area for individual server instances{color:#d04437}</li></ul>{color}"
> },
> }
> {panel}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFLY-8933) Description of path attributes in messaging subsystem contains HTML tags
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-8933?page=com.atlassian.jira.plugin.... ]
Romain Pelisse reassigned WFLY-8933:
------------------------------------
Assignee: Romain Pelisse (was: Jeff Mesnil)
> Description of path attributes in messaging subsystem contains HTML tags
> ------------------------------------------------------------------------
>
> Key: WFLY-8933
> URL: https://issues.jboss.org/browse/WFLY-8933
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 11.0.0.Alpha1
> Reporter: Romain Pelisse
> Assignee: Romain Pelisse
> Priority: Minor
>
> Description of attributes {{path}} and {{relative-to}} shown in CLI contains HTML tags.
> {noformat}
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/path=paging-directory:read-resource-description
> {noformat}
> {panel}
> "paging-directory" => {
> "path" => {
> "description" => "The actual filesystem path. Treated as an absolute path, unless the 'relative-to' attribute is specified, in which case the value is treated as relative to that path. {color:#d04437}<p>{color}If treated as an absolute path, the actual runtime pathname specified by the value of this attribute will be determined as follows: {color:#d04437}</p>{color}If this value is already absolute, then the value is directly used. Otherwise the runtime pathname is resolved in a system-dependent way. On UNIX systems, a relative pathname is made absolute by resolving it against the current user directory. On Microsoft Windows systems, a relative pathname is made absolute by resolving it against the current directory of the drive named by the pathname, if any; if not, it is resolved against the current user directory.",
> },
> "relative-to" => {
> "description" => "The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute. The standard paths provided by the system include:{color:#d04437}<ul><li>{color}jboss.home - the root directory of the JBoss AS distribution{color:#d04437}</li>{color}<li>user.home - user's home directory{color:#d04437}</li><li>{color}user.dir - user's current working directory</li><li>java.home - java installation directory{color:#d04437}</li><li>{color}jboss.server.base.dir - root directory for an individual server instance{color:#d04437}</li><li>{color}jboss.server.data.dir - directory the server will use for persistent data file storage{color:#d04437}</li><li>{color}jboss.server.log.dir - directory the server will use for log file storage{color:#d04437}</li><li>{color}jboss.server.tmp.dir - directory the server will use for temporary file storage{color:#d04437}</li><li>{color}jboss.domain.servers.dir - directory under which a host controller will create the working area for individual server instances{color:#d04437}</li></ul>{color}"
> },
> }
> {panel}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-2956) deployment of archive is stuck when command-timeout is set
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-2956:
--------------------------------------------
Summary: deployment of archive is stuck when command-timeout is set
Key: WFCORE-2956
URL: https://issues.jboss.org/browse/WFCORE-2956
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
Priority: Critical
Actually any command that would call back to the CommandContext for command execution would suffer from this problem. The CommandExecutor has a single thread executorService, it should have a pool of multiple threads.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (WFCORE-2410) Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2410?page=com.atlassian.jira.plugi... ]
Brian Stansberry reopened WFCORE-2410:
--------------------------------------
> Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2410
> URL: https://issues.jboss.org/browse/WFCORE-2410
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Ondrej Lukas
> Assignee: Chao Wang
> Labels: user_experience
> Fix For: 3.0.0.Beta27
>
>
> 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)
8 years, 11 months
[JBoss JIRA] (WFCORE-2410) Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2410?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2410:
------------------------------------------
Sorry, [~dmlloyd] I missed this comment and merged the PR. I'll revert it.
> Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2410
> URL: https://issues.jboss.org/browse/WFCORE-2410
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Ondrej Lukas
> Assignee: Chao Wang
> Labels: user_experience
> Fix For: 3.0.0.Beta27
>
>
> 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)
8 years, 11 months
[JBoss JIRA] (WFCORE-2410) Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2410?page=com.atlassian.jira.plugi... ]
David Lloyd commented on WFCORE-2410:
-------------------------------------
The technique of splitting the directory name in this way is referred to as "hashing". This Google query [1] turns up plenty of supporting information.
[1] https://www.google.com/search?q=directory+hashing
> Wrong resource and operation descriptions for Elytron filesystem-realm in management model and XSD
> --------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2410
> URL: https://issues.jboss.org/browse/WFCORE-2410
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.0.Beta7
> Reporter: Ondrej Lukas
> Assignee: Chao Wang
> Labels: user_experience
> Fix For: 3.0.0.Beta27
>
>
> 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)
8 years, 11 months