April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-868) credential-reference not able to use masked passwords

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/ELY-868?page=com.atlassian.jira.plugin.sy... ] Hynek Švábek resolved ELY-868. ------------------------------ Resolution: Done It was fixed yet. > credential-reference not able to use masked passwords > ----------------------------------------------------- > > Key: ELY-868 > URL: https://issues.jboss.org/browse/ELY-868 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Reporter: Peter Skopek > Assignee: Peter Skopek > > credential-reference cannot use PBE encrypted credentials AKA masked passwords (MASK-). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2485) CS tool, add prompt when --password is missing

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2485?page=com.atlassian.jira.plugi... ] Hynek Švábek resolved WFCORE-2485. ---------------------------------- Resolution: Done It was fixed yet. > CS tool, add prompt when --password is missing > ---------------------------------------------- > > Key: WFCORE-2485 > URL: https://issues.jboss.org/browse/WFCORE-2485 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > Labels: credential-store > > Use case: > - User have automation script using cs tool and user don't want to have password stored in file. > - User don't want credential store password to be stored in shell history after execution. > - User don't want credential store password to be listed in {{ps -aux}} output. > There have to be possibility to omit --password attribute. When omitting --password attribute user interaction prompt should follow with possibility to input password. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-411) Syntax error when applying patch and exiting jboss-cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-411?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-411: ------------------------------------------------ Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1408961|https://bugzilla.redhat.com/show_bug.cgi?id=1408961] from POST to MODIFIED > Syntax error when applying patch and exiting jboss-cli > ------------------------------------------------------ > > Key: WFCORE-411 > URL: https://issues.jboss.org/browse/WFCORE-411 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Patching > Reporter: Arun Gupta > Assignee: Alexey Loubyansky > > [disconnected /] patch apply > ../wildfly-8.1.0.Final-update/wildfly-8.1.0.Final.patch > { > "outcome" : "success", > "result" : {} > } > [disconnected /] > [disconnected /] > [disconnected /] > [disconnected /] exit > logging.configuration already set in JAVA_OPTS > ./bin/jboss-cli.sh: line 81: syntax error near unexpected token `fi' > ./bin/jboss-cli.sh: line 81: `fi' -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1346) IronJacamar isn't compatible with picketbox version used in WildFly

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1346?page=com.atlassian.jira.plugin... ] Martin Simka moved JBEAP-10153 to JBJCA-1346: --------------------------------------------- Project: IronJacamar (was: JBoss Enterprise Application Platform) Key: JBJCA-1346 (was: JBEAP-10153) Workflow: classic default workflow (was: CDW with loose statuses v1) Component/s: Build (was: JCA) Affects Version/s: WildFly/IronJacamar 1.4.2.Final (was: 7.1.0.DR15) > IronJacamar isn't compatible with picketbox version used in WildFly > ------------------------------------------------------------------- > > Key: JBJCA-1346 > URL: https://issues.jboss.org/browse/JBJCA-1346 > Project: IronJacamar > Issue Type: Bug > Components: Build > Affects Versions: WildFly/IronJacamar 1.4.2.Final > Reporter: Martin Simka > Assignee: Stefano Maestri > > Ironjacamar is compiled with Picketbox 4.0.19.Final and WildFly comes with 5.0.1.Final. These versions are not binary compatible, I'm getting > {noformat} > Caused by: java.lang.NoSuchMethodError: org.jboss.security.identity.RoleGroup.getRoles()Ljava/util/List; > at org.jboss.jca.core.security.picketbox.PicketBoxSecurityContext.getRoles(PicketBoxSecurityContext.java:76) > at org.jboss.as.test.integration.jca.security.WildFlyActivationRaWithSecurityDomainWorkManagerSecurityDomainTestCase$MyWork.run(WildFlyActivationRaWithSecurityDomainWorkManagerSecurityDomainTestCase.java:304) > at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223) > ... 6 more > {noformat} > signature changed in this case from {{List<Role> getRoles()}} to {{Collection<Role> getRoles()}} > I tried to compile IJ with 5.0.1 and my test then works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2628) DeploymentPlan doesn't have an operation to explode content

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-2628: ----------------------------------------- Summary: DeploymentPlan doesn't have an operation to explode content Key: WFCORE-2628 URL: https://issues.jboss.org/browse/WFCORE-2628 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Affects Versions: 3.0.0.Beta13 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Currently only deployments can be exploded while archive inside an exploded deployment should be explodeable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1046) Elytron properties-realm doesn't handle unicode sequences

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/ELY-1046?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski reassigned ELY-1046: --------------------------------------- Assignee: Bartosz Baranowski (was: Darran Lofthouse) > Elytron properties-realm doesn't handle unicode sequences > --------------------------------------------------------- > > Key: ELY-1046 > URL: https://issues.jboss.org/browse/ELY-1046 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Bartosz Baranowski > Priority: Blocker > Labels: eap71_beta_candidate > > Users who use property-file based authentication with plain passwords can't authenticate with Elytron if the property file contains Unicode escape sequences (e.g. file generated by using a classical {{java.util.Properties}}). The same authentication works with legacy solution (_/core-service=management/security-realm=ApplicationRealm/authentication=properties(plain-text=true, ...)_). > The {{LegacyPropertiesSecurityRealm}} implementation has to be able to support properties files which were supported by legacy security realms. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-138) java.lang.UnsatisfiedLinkError: Can't find SAPI class using PHP module

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/JBWEB-138?page=com.atlassian.jira.plugin.... ] Jean-Frederic Clere resolved JBWEB-138. --------------------------------------- Resolution: Out of Date > java.lang.UnsatisfiedLinkError: Can't find SAPI class using PHP module > ---------------------------------------------------------------------- > > Key: JBWEB-138 > URL: https://issues.jboss.org/browse/JBWEB-138 > Project: JBoss Web > Issue Type: Bug > Components: Tomcat > Affects Versions: JBossWeb-2.1.2.GA > Environment: Windows XP, JDK 1.6.0 > Reporter: Derek Cornelius > Assignee: Mladen Turk > > The php5sevlet.dll is loaded and uses JNI to load the org.jboss.web.php.SAPI class which fails returning NULL. > The SAPI class should be in class path since the DLL is loaded by the Library.java > . > Apr 21, 2009 5:11:45 PM org.apache.catalina.core.StandardContext loadOnStartup > SEVERE: Servlet /php-examples.war threw load() exception > java.lang.UnsatisfiedLinkError: Can't find SAPI class, no libphp5servlet in java.library.path(C:\jdk1.6.0_07\bin;.;C:\WINXP\Sun\Java\bin;C:\WINXP\system32;C:\WINXP;C:\RetAdv\Trunk/DevRoot/rai-jboss/src/jboss-web-2.1.2.GA\PHP\bin;C:\RetAdv\Trunk/DevRoot/rai-jboss/src/jboss-web-2.1.2.GA/bin;C:\RetAdv\Trunk/DevRoot/rai-jboss/src/jboss-web-2.1.2.GA/bin;...) > at org.jboss.web.php.Library.<init>(Library.java:65) > at org.jboss.web.php.Library.initialize(Library.java:104) > at org.jboss.web.php.Handler.init(Handler.java:104) > at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) > at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:950) > at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4122) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4421) > at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:800) > at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:780) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) > at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:631) > at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:557) > at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492) > at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1211) > at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:315) > at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1064) > at org.apache.catalina.core.StandardHost.start(StandardHost.java:718) > at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1056) > at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) > at org.apache.catalina.core.StandardService.start(StandardService.java:523) > at org.apache.catalina.core.StandardServer.start(StandardServer.java:736) > at org.apache.catalina.startup.Catalina.start(Catalina.java:575) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2627) CLI, slow tests

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-2627: -------------------------------------------- Summary: CLI, slow tests Key: WFCORE-2627 URL: https://issues.jboss.org/browse/WFCORE-2627 Project: WildFly Core Issue Type: Bug Components: CLI, Test Suite Reporter: Jean-Francois Denise Assignee: Tomaz Cerar org.jboss.as.test.integration.management.cli.CliAliasTestCase consumes an extra 20sec org.jboss.as.test.integration.management.cli.CliConfigTestCase consumes an extra 40sec By fixing these 2 tests, 1 minute gain should be expected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2627) CLI, slow tests

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2627?page=com.atlassian.jira.plugi... ] Jean-Francois Denise reassigned WFCORE-2627: -------------------------------------------- Assignee: Jean-Francois Denise (was: Tomaz Cerar) > CLI, slow tests > --------------- > > Key: WFCORE-2627 > URL: https://issues.jboss.org/browse/WFCORE-2627 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Test Suite > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > org.jboss.as.test.integration.management.cli.CliAliasTestCase consumes an extra 20sec > org.jboss.as.test.integration.management.cli.CliConfigTestCase consumes an extra 40sec > By fixing these 2 tests, 1 minute gain should be expected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8161) JDR Subsystem destroys password related system properties

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-8161?page=com.atlassian.jira.plugin.... ] Marek Kopecký reopened WFLY-8161: --------------------------------- Reopen, verification fail, new regexp for passwords is "password=.*", original regexp was ".*password.*". So for example, "-Da_password_b=bbb" system properties was stored to zip file: * before actual PR: a_password_b=<Redacted> * after actual PR: a_password_b=bbb > JDR Subsystem destroys password related system properties > --------------------------------------------------------- > > Key: WFLY-8161 > URL: https://issues.jboss.org/browse/WFLY-8161 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 10.0.0.Final, 10.1.0.Final > Reporter: John Mazzitelli > Assignee: Brad Maxwell > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > When you export a JDR, it provides a report of system properties, but to avoid leaking passwords, it redacts any system property with the string <Redacted> - see here: > https://github.com/wildfly/wildfly/blob/master/jdr/jboss-as-jdr/src/main/... > One major problem is it never flips the system properties back to their original values! So once a JDR report is created, no code in the JVM can ever be able to use those password system properties again - because the password is now changed to the string "<Redacted>". > To fix, once that "system-properties.txt" file is created, you have to System.setProperty() those password properties back to their original values. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 April 2017