January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1652) The security realm PlugIns are currently returning roles, this should be group membership information.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-1652?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-1652: ----------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > The security realm PlugIns are currently returning roles, this should be group membership information. > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-1652 > URL: https://issues.jboss.org/browse/WFLY-1652 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 9.0.0.CR1 > > > Without breaking backwards compatibility this should be returning group membership information and not roles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2489) Replace add-user example image with something not running as root.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2489?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2489: ----------------------------------- Fix Version/s: 8.0.1.Final (was: 8.0.0.Final) > Replace add-user example image with something not running as root. > ------------------------------------------------------------------ > > Key: WFLY-2489 > URL: https://issues.jboss.org/browse/WFLY-2489 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Console > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > Where no users are defined we show a web page with an example using the add user utility - would be a good idea to not be encouraging running as root. > In addition to this some of the prompts have evolved anyway e.g. no longer a need to specify the realm name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2456) Using add-user.bat for initial admin user results in "JBAS015234: No mgmt-groups.properties files found"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2456?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2456: ----------------------------------- Fix Version/s: 8.0.1.Final (was: 9.0.0.CR1) > Using add-user.bat for initial admin user results in "JBAS015234: No mgmt-groups.properties files found" > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-2456 > URL: https://issues.jboss.org/browse/WFLY-2456 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.0.0.Beta1 > Environment: Windows 7, 32-bit, jdk1.7.0_45 > Reporter: John Lusk > Assignee: Darran Lofthouse > Fix For: 8.0.1.Final > > > Just getting started w/Wildfly after a long absence from Java. Fresh download, trying to hit admin console, got instructed to use add-user to add an admin user. > c:\usr\local\wildfly-8.0.0.Beta1\bin>.\add-user.bat > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > * Error * > JBAS015234: No mgmt-groups.properties files found. > Press any key to continue . . . > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JBOSS_HOME% > C:\usr\local\wildfly-8.0.0.Beta1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %JAVA_HOME% > C:\java\jdk1.7.0_45 > c:\usr\local\wildfly-8.0.0.Beta1\bin>echo %M2_HOME% > C:\usr\local\Maven\3.1.1 > c:\usr\local\wildfly-8.0.0.Beta1\bin>mvn -version > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:2 > 2-0400) > Maven home: C:\usr\local\Maven\3.1.1 > Java version: 1.7.0_45, vendor: Oracle Corporation > Java home: C:\java\jdk1.7.0_45\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" > c:\usr\local\wildfly-8.0.0.Beta1\bin> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-566) Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-566?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated WFLY-566: ---------------------------------- Fix Version/s: 8.0.0.Final (was: 9.0.0.CR1) > Using pre-digested passwords, having all installations with the same realm could reduce the effectiveness > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-566 > URL: https://issues.jboss.org/browse/WFLY-566 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: Realm_Management > Fix For: 8.0.0.Final > > > Can we generate a name of first boot? Possibly even separate the internal name use to link from the realm to the name presented to the end users? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2672) Additional debug logging for LDAP based group loading.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2672?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2672: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1044772|https://bugzilla.redhat.com/show_bug.cgi?id=1044772] from POST to MODIFIED > Additional debug logging for LDAP based group loading. > ------------------------------------------------------ > > Key: WFLY-2672 > URL: https://issues.jboss.org/browse/WFLY-2672 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2739) BeanDeploymentArchive for external (WFLY) modules added twice

by Pëtr Andreev (JIRA)

[ https://issues.jboss.org/browse/WFLY-2739?page=com.atlassian.jira.plugin.... ] Pëtr Andreev commented on WFLY-2739: ------------------------------------ Pull Request: https://github.com/wildfly/wildfly/pull/5828 > BeanDeploymentArchive for external (WFLY) modules added twice > ------------------------------------------------------------- > > Key: WFLY-2739 > URL: https://issues.jboss.org/browse/WFLY-2739 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.CR1 > Environment: Win7,CentOS6 > Reporter: Pëtr Andreev > Assignee: Jozef Hartinger > Fix For: 8.0.0.Final > > > The Weld-WFLY integration adds a dependency on WFLY module twice if the application deployment unit is an EAR containg libs, ejbs, war, etc. It prevents an application having dependencies on a new Picketlink (PL) extension to be deployed since PL contains a portable extension which has to be injected within PL module. The Weld-validation of the second time injection fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-388) Inconsistent behavior of "contains" operator

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-388?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-388. -------------------------------- Fix Version/s: 6.1.0.Beta1 Resolution: Done > Inconsistent behavior of "contains" operator > -------------------------------------------- > > Key: DROOLS-388 > URL: https://issues.jboss.org/browse/DROOLS-388 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Minor > Fix For: 6.1.0.Beta1 > > > The compiler accepts constraints such as > {code} > Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') > {code} > Interestingly, MVEL evaluates it as the string operation "contains", but > once the constraint is jitted it is again evaluated as a collection operator. > That is, a rule such as: > {code} > when > $s : String( this contains "foo" ) > then > {code} > with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-388) Inconsistent behavior of "contains" operator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-388?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-388: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1060033|https://bugzilla.redhat.com/show_bug.cgi?id=1060033] from NEW to ASSIGNED > Inconsistent behavior of "contains" operator > -------------------------------------------- > > Key: DROOLS-388 > URL: https://issues.jboss.org/browse/DROOLS-388 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Minor > > The compiler accepts constraints such as > {code} > Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') > {code} > Interestingly, MVEL evaluates it as the string operation "contains", but > once the constraint is jitted it is again evaluated as a collection operator. > That is, a rule such as: > {code} > when > $s : String( this contains "foo" ) > then > {code} > with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-388) Inconsistent behavior of "contains" operator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-388?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-388: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060033 > Inconsistent behavior of "contains" operator > -------------------------------------------- > > Key: DROOLS-388 > URL: https://issues.jboss.org/browse/DROOLS-388 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.1.Final, 6.0.0.Final > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Minor > > The compiler accepts constraints such as > {code} > Person( fullName contains 'Jr' ) // should be fullName.contains('Jr') > {code} > Interestingly, MVEL evaluates it as the string operation "contains", but > once the constraint is jitted it is again evaluated as a collection operator. > That is, a rule such as: > {code} > when > $s : String( this contains "foo" ) > then > {code} > with inputs "foo1" .. "fooN" effectively fires an unpredictable number of times before starting to fail silently -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2785) master reload on windows using bind IP without a reverse DNS entry (or a wrong one)

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFLY-2785?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber reassigned WFLY-2785: ----------------------------------------- Assignee: Aleksandar Kostadinov (was: Emanuel Muckenhuber) Once your PR is merged, you can resolve this issue. Thanks > master reload on windows using bind IP without a reverse DNS entry (or a wrong one) > ----------------------------------------------------------------------------------- > > Key: WFLY-2785 > URL: https://issues.jboss.org/browse/WFLY-2785 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0.0.CR1 > Environment: windows > Reporter: Aleksandar Kostadinov > Assignee: Aleksandar Kostadinov > Labels: addressing, domain, socket > Attachments: server_logs.zip > > > When running on windows and the server management port bind IP address does not have a proper reverse DNS entry or an entry in the hosts file, then there is trouble reloading the server. It is possible that same issue may affect other domain server management operations but I didn't identify any others (and didn't try). > Basically the problem is that windows reverse resolves such IPs to the computer name. On reload without restarting the managed servers, they receive as a host to reconnect to the computer name instead of the IP address and connection cannot be established. > Here is how to reproduce: > # on a windows machine add some local IP address without a reverse entry (e.g. 192.0.2.15) > # launch domain server from wildfly, e.g.: bin/domain.sh -bpublic=192.0.2.15 -bmanagement=192.0.2.15 > # issue this cli command: reload --restart-servers=false --host=master > # see logs for messages from server-one and server-two (I'll attach an archive with such logs) > The fix I found for the issue is:{CODE} > diff --git a/host-controller/src/main/java/org/jboss/as/host/controller/ManagedServer.java b/host-controller/src/main/java/org/jboss/as/host/controller/ManagedServer.java > index 308df0e..c6a88e8 100644 > --- a/host-controller/src/main/java/org/jboss/as/host/controller/ManagedServer.java > +++ b/host-controller/src/main/java/org/jboss/as/host/controller/ManagedServer.java > @@ -30,7 +30,6 @@ import static org.jboss.as.host.controller.HostControllerLogger.ROOT_LOGGER; > > import java.io.IOException; > import java.io.OutputStream; > -import java.net.InetAddress; > import java.net.InetSocketAddress; > import java.util.Collections; > import java.util.LinkedHashMap; > @@ -769,7 +768,7 @@ class ManagedServer { > public boolean execute(ManagedServer server) throws Exception { > assert Thread.holdsLock(ManagedServer.this); // Call under lock > // Reconnect > - final String hostName = InetAddress.getByName(managementSocket.getHostName()).getHostName(); > + final String hostName = managementSocket.getHostString(); > final int port = managementSocket.getPort(); > processControllerClient.reconnectProcess(serverProcessName, NetworkUtils.formatPossibleIpv6Address(hostName), port, bootConfiguration.isManagementSubsystemEndpoint(), authKey); > return true; > {CODE} > I see that the line causing the troubles was [committed|https://github.com/wildfly/wildfly/commit/7effc2eca6cfd5d031a05...] as part of AS7-3613. I looked at the issue and I don't see how this altering of hostname can help with getting a good URI. Yes, it can help if it guaranteed that a hostname will always be returned but fact is that on linux, if reverse record is missing or improper, this still returns an IP so this line of code IMO can only cause harm. Am I missing something? > Moreover it doesn't seems right to me to change server identification overriding user choice to select an IP instead of a hostname just to fix some URIs. > IMO if user/administrator used an IP, then server should to use it as an IP, not reverse resolve it to a host and then use it. It simply leads to confusion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 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 January 2014