July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-134) Add module name, module version fields to ExtLogRecord

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-134?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-134: --------------------------------- Fix Version/s: 2.1.0.Alpha3 (was: 2.1.0.Alpha2) > Add module name, module version fields to ExtLogRecord > ------------------------------------------------------ > > Key: LOGMGR-134 > URL: https://issues.jboss.org/browse/LOGMGR-134 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha3 > > > It will be necessary for ExtLogRecord to carry additional fields for Java 9 module name and module version. The serialization impact should be analyzed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6573) Allow Vault encrypted strings to be updated without a restart

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6573: -------------------------------------- Assignee: (was: Darran Lofthouse) > Allow Vault encrypted strings to be updated without a restart > ------------------------------------------------------------- > > Key: WFLY-6573 > URL: https://issues.jboss.org/browse/WFLY-6573 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > > When a new vault string is created the affected servers in the domain have to be restarted before the encrypted value is applied. This makes it difficult to test a new configuration in CLI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6569) Vault.sh can create keystore when doesn't exist. But we can't define KEY_SIZE for it.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6569?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6569: -------------------------------------- Assignee: (was: Darran Lofthouse) > Vault.sh can create keystore when doesn't exist. But we can't define KEY_SIZE for it. > ------------------------------------------------------------------------------------- > > Key: WFLY-6569 > URL: https://issues.jboss.org/browse/WFLY-6569 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > > Vault.sh can create keystore when doesn't exist. But we can't define KEY_SIZE for it. > Vault.sh have -t, --create-keystore parameter for create new keystore when it doesn't exist. > But we need define KEY_SIZE too in other case KEY_SIZE = 128 is used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6823) Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6823?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6823: ----------------------------------- Fix Version/s: (was: 11.0.0.Beta1) > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > ----------------------------------------------------------------------------------------- > > Key: WFLY-6823 > URL: https://issues.jboss.org/browse/WFLY-6823 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > We noticed it when we looked on JIra issue https://issues.jboss.org/browse/JBEAP-3603. > We JBoss EAP 7 expects encoded UTF-8 strings in code. But we didn't find any information about it in specification. > It works with Chrome and Opera, but it doesn't work with Firefox. > Since there is no documentation for this username/password limitation it can affect customers who want to use non-ASCII credentials. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6657) permissions.xml is not parsed if -Dorg.jboss.server.bootstrap.maxThreads is explicitly set

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6657?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6657: -------------------------------------- Assignee: (was: Darran Lofthouse) > permissions.xml is not parsed if -Dorg.jboss.server.bootstrap.maxThreads is explicitly set > ------------------------------------------------------------------------------------------ > > Key: WFLY-6657 > URL: https://issues.jboss.org/browse/WFLY-6657 > Project: WildFly > Issue Type: Bug > Components: Security, Security Manager > Affects Versions: 8.2.0.Final, 9.0.1.Final > Environment: Reproduced on both Windows and RedHat machines. > Reporter: Marius Ani > Priority: Minor > > If -Dorg.jboss.server.bootstrap.maxThreads is explictily set in Wildfly, then, the permissions.xml file is not even parsed when the application is deployed. > Debugging the Wildfly 8.2.0 source code revealed the problem in org.jboss.as.server.ServerService#addService:218 > {code:java} > if (configuration.getServerEnvironment().isAllowModelControllerExecutor()) { > serviceBuilder.addDependency(Services.JBOSS_SERVER_EXECUTOR, ExecutorService.class, service.getExecutorServiceInjector()); > } > {code} > The org.jboss.as.server.ServerEnvironment#allowModelControllerExecutor property is set to true if -Dorg.jboss.server.bootstrap.maxThreads was set. > The above 'if' seems a little strange because a default value for maxThreads is always set in org.jboss.as.server.ServerEnvironment#getBootstrapMaxThreads even when the -Dorg.jboss.server.bootstrap.maxThreads property was not specified. > This may also cause other things to not work properly when -Dorg.jboss.server.bootstrap.maxThreads is set. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6881) User with password which contains chinese chars isn't able to log in to AD (on Windows).

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6881?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6881: -------------------------------------- Assignee: (was: Darran Lofthouse) > User with password which contains chinese chars isn't able to log in to AD (on Windows). > ---------------------------------------------------------------------------------------- > > Key: WFLY-6881 > URL: https://issues.jboss.org/browse/WFLY-6881 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Priority: Minor > > We have a problem log in to AD on Windows. When user has password with chinese chars he cannot log in. > My observations: > I found out this: If I create AD entries from linux and update testsuite for using this entries (not creating own) then it is ok. > I wasn't able to find out where is the exact problem. In my opinion there is some problem with creating AD user password on windows. > Workaround: > Creating AD data in other way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6823) Doesn't work using non-ASCII chars for username and/or password for BASIC authentication.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6823?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6823: -------------------------------------- Assignee: (was: Darran Lofthouse) > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > ----------------------------------------------------------------------------------------- > > Key: WFLY-6823 > URL: https://issues.jboss.org/browse/WFLY-6823 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Fix For: 11.0.0.Beta1 > > > Doesn't work using non-ASCII chars for username and/or password for BASIC authentication. > We noticed it when we looked on JIra issue https://issues.jboss.org/browse/JBEAP-3603. > We JBoss EAP 7 expects encoded UTF-8 strings in code. But we didn't find any information about it in specification. > It works with Chrome and Opera, but it doesn't work with Firefox. > Since there is no documentation for this username/password limitation it can affect customers who want to use non-ASCII credentials. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6925) vault-tool adds invalid character to "ENC_FILE_DIR"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6925?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6925: -------------------------------------- Assignee: (was: Darran Lofthouse) > vault-tool adds invalid character to "ENC_FILE_DIR" > --------------------------------------------------- > > Key: WFLY-6925 > URL: https://issues.jboss.org/browse/WFLY-6925 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Krashan Brahmanjara > Priority: Trivial > > vault-tool executed on Windows adds invalid character to "ENC_FILE_DIR" > for example this > {code:java} > <vault-option name="ENC_FILE_DIR" value="./vault\"/> > {code} > instead > {code:java} > <vault-option name="ENC_FILE_DIR" value="./vault/"/> > {code} > Second code also works on Windows and can be easily used on linux. > Test command: > vault.bat --keystore key.store --keystore-password abc123 --alias Vault --vault-block ws --attribute ws-user1 --sec-attr passwd --enc-dir ./vault --iteration 95 --salt ABCD1234 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6907) Add log message with information that there is replacement (Credential Store) for Vaults

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6907?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-6907. ------------------------------------ Fix Version/s: 11.0.0.Beta1 Resolution: Done > Add log message with information that there is replacement (Credential Store) for Vaults > ---------------------------------------------------------------------------------------- > > Key: WFLY-6907 > URL: https://issues.jboss.org/browse/WFLY-6907 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > Fix For: 11.0.0.Beta1 > > > There will be replacement for deprecated Password Vault System. > It would be nice add there some log message e.g.: "Vaults are deprecated, please check Credential Store". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7009) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.security

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7009?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7009: -------------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.security > ------------------------------------------------------------------------------------------------- > > Key: WFLY-7009 > URL: https://issues.jboss.org/browse/WFLY-7009 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > > This cap was introduced to support an optional requirement for transaction manager integration. Both sides of this contract need examination. > Note that the task here is not to just create a meaningless entry. Once the entry is published a contract is established, so the contract has to be correct. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2017