May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6656) add-user.sh does not return the secret value in non-interactive mode.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6656?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6656: -------------------------------------- Assignee: (was: Darran Lofthouse) > add-user.sh does not return the secret value in non-interactive mode. > --------------------------------------------------------------------- > > Key: WFLY-6656 > URL: https://issues.jboss.org/browse/WFLY-6656 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Petros Petrou > Priority: Minor > Fix For: Awaiting Volunteers > > > Running add-user.sh in non-interactive mode does not return the secret value of the password. It would be a useful feature when automating user creation using platform build software. > Non-Interactive Mode > ============= > add-user.sh --user domainuser --password welcome1! > Added user 'domainuser' to file '\opt\wildfly-10.0.0\standalone\configuration\mgmt-users.properties' > Added user 'domainuser' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties' > Press any key to continue . . . > Interactive Mode > ============= > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > Enter the details of the new user to add. > Using realm 'ManagementRealm' as discovered from the existing property files. > Username : ppetrou > Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file. > - The password should be different from the username > - The password should not be one of the following restricted values {root, admin, administrator} > - The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s) > Password : > Re-enter Password : > What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]: > About to add user 'ppetrou' for realm 'ManagementRealm' > Is this correct yes/no? yes > Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-users.properties' > Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties' > Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-groups.properties' > Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-groups.properties' > Is this new user going to be used for one AS process to connect to another AS process? > e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls. > yes/no? yes > To represent the user add the following to the server-identities definition <secret value="d2VsY29tZTEh" /> > Press any key to continue . . . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

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

by Marius Ani (JIRA)

Marius Ani created WFLY-6657: -------------------------------- Summary: 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: 9.0.1.Final, 8.2.0.Final Environment: Reproduced on both Windows and RedHat machines. Reporter: Marius Ani Assignee: Darran Lofthouse 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 (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6656) add-user.sh does not return the secret value in non-interactive mode.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6656?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-6656: --------------------------------- Assignee: Darran Lofthouse (was: Tomaz Cerar) > add-user.sh does not return the secret value in non-interactive mode. > --------------------------------------------------------------------- > > Key: WFLY-6656 > URL: https://issues.jboss.org/browse/WFLY-6656 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Petros Petrou > Assignee: Darran Lofthouse > Priority: Minor > > Running add-user.sh in non-interactive mode does not return the secret value of the password. It would be a useful feature when automating user creation using platform build software. > Non-Interactive Mode > ============= > add-user.sh --user domainuser --password welcome1! > Added user 'domainuser' to file '\opt\wildfly-10.0.0\standalone\configuration\mgmt-users.properties' > Added user 'domainuser' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties' > Press any key to continue . . . > Interactive Mode > ============= > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > Enter the details of the new user to add. > Using realm 'ManagementRealm' as discovered from the existing property files. > Username : ppetrou > Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file. > - The password should be different from the username > - The password should not be one of the following restricted values {root, admin, administrator} > - The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s) > Password : > Re-enter Password : > What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]: > About to add user 'ppetrou' for realm 'ManagementRealm' > Is this correct yes/no? yes > Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-users.properties' > Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties' > Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-groups.properties' > Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-groups.properties' > Is this new user going to be used for one AS process to connect to another AS process? > e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls. > yes/no? yes > To represent the user add the following to the server-identities definition <secret value="d2VsY29tZTEh" /> > Press any key to continue . . . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6656) add-user.sh does not return the secret value in non-interactive mode.

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6656?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6656: ------------------------------ Component/s: (was: Scripts) > add-user.sh does not return the secret value in non-interactive mode. > --------------------------------------------------------------------- > > Key: WFLY-6656 > URL: https://issues.jboss.org/browse/WFLY-6656 > Project: WildFly > Issue Type: Enhancement > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Petros Petrou > Assignee: Tomaz Cerar > Priority: Minor > > Running add-user.sh in non-interactive mode does not return the secret value of the password. It would be a useful feature when automating user creation using platform build software. > Non-Interactive Mode > ============= > add-user.sh --user domainuser --password welcome1! > Added user 'domainuser' to file '\opt\wildfly-10.0.0\standalone\configuration\mgmt-users.properties' > Added user 'domainuser' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties' > Press any key to continue . . . > Interactive Mode > ============= > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > Enter the details of the new user to add. > Using realm 'ManagementRealm' as discovered from the existing property files. > Username : ppetrou > Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file. > - The password should be different from the username > - The password should not be one of the following restricted values {root, admin, administrator} > - The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s) > Password : > Re-enter Password : > What groups do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]: > About to add user 'ppetrou' for realm 'ManagementRealm' > Is this correct yes/no? yes > Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-users.properties' > Added user 'ppetrou' to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-users.properties' > Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\standalone\configuration\mgmt-groups.properties' > Added user 'ppetrou' with groups to file '\opt\wildfly-10.0.0.Final\domain\configuration\mgmt-groups.properties' > Is this new user going to be used for one AS process to connect to another AS process? > e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls. > yes/no? yes > To represent the user add the following to the server-identities definition <secret value="d2VsY29tZTEh" /> > Press any key to continue . . . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1543) Upgrade Undertow to 1.3.22

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1543?page=com.atlassian.jira.plugi... ] Stuart Douglas resolved WFCORE-1543. ------------------------------------ Fix Version/s: 3.0.0.Alpha2 Resolution: Done > Upgrade Undertow to 1.3.22 > -------------------------- > > Key: WFCORE-1543 > URL: https://issues.jboss.org/browse/WFCORE-1543 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Mathieu Lachance > Assignee: Stuart Douglas > Fix For: 3.0.0.Alpha2, 2.2.0.Final > > > If it's not too late for the Wildfly 10.1.0.Final release, I'd like to benefits from UNDERTOW-707 which is contained in Undertow 1.3.22.Final. > Thanks. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook)

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Bela Ban reassigned JGRP-2063: ------------------------------ Assignee: Bela Ban (was: Radoslav Husar) > JDBC_PING: allow supplying dataSource object directly (e.g. via after_creation_hook) > ------------------------------------------------------------------------------------ > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Bela Ban > Fix For: 3.6.10, 4.0 > > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1127) Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1127?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1127: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from POST to MODIFIED > Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1127 > URL: https://issues.jboss.org/browse/DROOLS-1127 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Any code that does `new Thread()` on GAE throws an exception, because you can't create new threads yourself. > Other future cloud platforms might have a similar restriction. It should be possible to plug in a custom way of creating threads. > *Proposal A)* Add a kieBase configuration property to change the ThreadFactory > {code} > drools.threadFactory = com.user.project.GoogleAppEngineThreadFactory > {code} > *Proposal B)* Add a kieBase configuration property to change the ExecutorServiceFactory > {code} > drools.executorServiceFactory = com.user.project.ExecutorServiceFactory > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1125) Google App Engine support: ClassLoader.getSystemClassLoader() throws exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1125?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1125: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from POST to MODIFIED > Google App Engine support: ClassLoader.getSystemClassLoader() throws exception > ------------------------------------------------------------------------------ > > Key: DROOLS-1125 > URL: https://issues.jboss.org/browse/DROOLS-1125 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Class org.kie.internal.utils.ChainedProperties > Every call to get the System Class Loader > confClassLoader = ClassLoader.getSystemClassLoader(); (i.e. lines 133, 169) > raises an exception. > Todo: figure out which particular exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1125) Google App Engine support: ClassLoader.getSystemClassLoader() throws exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1125?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1125: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from ASSIGNED to POST > Google App Engine support: ClassLoader.getSystemClassLoader() throws exception > ------------------------------------------------------------------------------ > > Key: DROOLS-1125 > URL: https://issues.jboss.org/browse/DROOLS-1125 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Class org.kie.internal.utils.ChainedProperties > Every call to get the System Class Loader > confClassLoader = ClassLoader.getSystemClassLoader(); (i.e. lines 133, 169) > raises an exception. > Todo: figure out which particular exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1127) Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1127?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1127: ------------------------------------------------- Xiong Zhi Ming <zxiong(a)redhat.com> changed the Status of [bug 1329093|https://bugzilla-qe-05.host.stage.eng.rdu2.redhat.com/show_bug.cg...] from ASSIGNED to POST > Google App Engine support: Do not call new Thread() by allowing to plug in a custom ThreadFactory > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-1127 > URL: https://issues.jboss.org/browse/DROOLS-1127 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Fix For: 7.0.0.Beta1 > > > Any code that does `new Thread()` on GAE throws an exception, because you can't create new threads yourself. > Other future cloud platforms might have a similar restriction. It should be possible to plug in a custom way of creating threads. > *Proposal A)* Add a kieBase configuration property to change the ThreadFactory > {code} > drools.threadFactory = com.user.project.GoogleAppEngineThreadFactory > {code} > *Proposal B)* Add a kieBase configuration property to change the ExecutorServiceFactory > {code} > drools.executorServiceFactory = com.user.project.ExecutorServiceFactory > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2016