December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-871: --------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1170762, https://bugzilla.redhat.com/show_bug.cgi?id=1170764 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1170762) > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated SECURITY-871: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1170762 > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-871) AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault

by Derek Horton (JIRA)

[ https://issues.jboss.org/browse/SECURITY-871?page=com.atlassian.jira.plug... ] Derek Horton updated SECURITY-871: ---------------------------------- Summary: AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault (was: AdvancedLdapLoginModule should be able to retrieve password from Vault) Description: AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault (was: AdvancedLdapLoginModule should be able to retrieve password from Vault) > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault > ---------------------------------------------------------------------------- > > Key: SECURITY-871 > URL: https://issues.jboss.org/browse/SECURITY-871 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Reporter: Derek Horton > Assignee: Darran Lofthouse > > AdvancedLdapLoginModule should be able to retrieve bindCredential from Vault -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-267) CLI prints output twice if using cli client jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-267?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-267: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1149526 > CLI prints output twice if using cli client jar > ----------------------------------------------- > > Key: WFCORE-267 > URL: https://issues.jboss.org/browse/WFCORE-267 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha13 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.0.0.Alpha14 > > > If you are using the [CLI client jar|https://developer.jboss.org/wiki/UsingTheCLIRemoteClientJar], all output is printed twice. This is because JBoss logging is not set up and by default CommandContextImpl is printing log messages to standard out. The output will look something like this: > {code} > [standalone@localhost:9999 /] :read-children-types > Nov 19, 2014 8:57:19 AM org.jboss.as.cli.impl.CommandContextImpl printLine > INFO: { > "outcome" => "success", > "result" => [ > "core-service", > "deployment", > "deployment-overlay", > "extension", > "interface", > "path", > "socket-binding-group", > "subsystem", > "system-property" > ] > } > { > "outcome" => "success", > "result" => [ > "core-service", > "deployment", > "deployment-overlay", > "extension", > "interface", > "path", > "socket-binding-group", > "subsystem", > "system-property" > ] > } > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-650: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1168747|https://bugzilla.redhat.com/show_bug.cgi?id=1168747] from ASSIGNED to MODIFIED > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-650: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1168747|https://bugzilla.redhat.com/show_bug.cgi?id=1168747] from NEW to ASSIGNED > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-446) Provide an 'enable' parameter to the 'full-replace-deployment' operation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-446?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-4154 to WFCORE-446: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-446 (was: WFLY-4154) Component/s: Domain Management (was: Domain Management) Fix Version/s: 1.0.0.Beta1 (was: 9.0.0.Beta1) > Provide an 'enable' parameter to the 'full-replace-deployment' operation > ------------------------------------------------------------------------ > > Key: WFCORE-446 > URL: https://issues.jboss.org/browse/WFCORE-446 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 1.0.0.Beta1 > > > Similar to the /deployment=*:add() operation the /:full-replace-deployment() operarion should provide an 'enable' parameter that defines wether or not the deplyment should be enabled after the reaplcement. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-102) Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-102?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-102: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly-core/pull/182 > Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-102 > URL: https://issues.jboss.org/browse/WFCORE-102 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha9 > > > The various base classes OSH authors use to create handlers force the author to deal with ServiceVerificationHandler and, during rollback, with removing any services the OSH added. This task is to have the OperationContext handle these things transparently, removing the need for authors to do so. > To preserve compatibility, the various API methods authors may have overridden that expose the SVH and the list of added ServiceControllers will be retained (but deprecated), but the SVH and the list of handlers won't be used. The API javadoc will encourage use of method variants that don't use these parameters. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-118) Support suppressed exceptions in log formatting

by David Lloyd (JIRA)

David Lloyd created LOGMGR-118: ---------------------------------- Summary: Support suppressed exceptions in log formatting Key: LOGMGR-118 URL: https://issues.jboss.org/browse/LOGMGR-118 Project: JBoss Log Manager Issue Type: Feature Request Components: core Reporter: David Lloyd In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTEST-21) Intermittent fail of DataSourceOperationsUnitTestCase on IBM JDK 1.6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTEST-21?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTEST-21: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1100839|https://bugzilla.redhat.com/show_bug.cgi?id=1100839] from POST to ASSIGNED > Intermittent fail of DataSourceOperationsUnitTestCase on IBM JDK 1.6 > -------------------------------------------------------------------- > > Key: JBTEST-21 > URL: https://issues.jboss.org/browse/JBTEST-21 > Project: JBoss Test > Issue Type: Bug > Environment: IBM JDK > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > > When test DataSourceOperationsUnitTestCase is build with IBM JDK 1.6 it fails with error : > Tests in error: > org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase: [SHRINKWRAP-93] Cannot use this JDK-based implementation to export as ZIP an archive with no content: 314225ff-6abf-4453-b69b-7dd12b707d65.jar: 0 assets > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 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 December 2014