February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2158) NPE from org.apache.log4j.CategoryKey.

by Biswajit Bhuyan (JIRA)

Biswajit Bhuyan created JGRP-2158: ------------------------------------- Summary: NPE from org.apache.log4j.CategoryKey. Key: JGRP-2158 URL: https://issues.jboss.org/browse/JGRP-2158 Project: JGroups Issue Type: Bug Affects Versions: 3.6.11 Reporter: Biswajit Bhuyan Assignee: Bela Ban Getting NPE from jGroup. Please find the stacktrace below: java.lang.NullPointerException at org.apache.log4j.CategoryKey.<init>(CategoryKey.java:32) at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:266) at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:247) at org.apache.log4j.LogManager.getLogger(LogManager.java:228) at org.apache.log4j.Logger.getLogger(Logger.java:104) at com.webmethods.rtl.util.Debug$JuliToLog4jHandler.getTargetLogger(Debug.java:1798) at com.webmethods.rtl.util.Debug$JuliToLog4jHandler.publish(Debug.java:1790) at java.util.logging.Logger.log(Logger.java:738) at org.jgroups.logging.JDKLogImpl.log(JDKLogImpl.java:49) at org.jgroups.logging.JDKLogImpl.log(JDKLogImpl.java:28) at org.jgroups.logging.JDKLogImpl.warn(JDKLogImpl.java:122) at org.jgroups.stack.Configurator.setDefaultValues(Configurator.java:754) at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:117) at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:57) at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:476) at org.jgroups.JChannel.init(JChannel.java:852) at org.jgroups.JChannel.<init>(JChannel.java:159) at org.jgroups.JChannel.<init>(JChannel.java:148) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-33) [QE] - JMAN4-188 - Secure link from CloudForms to MW Provider

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-33?page=com.atlassian.jira.plu... ] Vojtech Prusa reassigned HAWKULARQE-33: --------------------------------------- Assignee: Vojtech Prusa (was: mfoley user) > [QE] - JMAN4-188 - Secure link from CloudForms to MW Provider > ------------------------------------------------------------- > > Key: HAWKULARQE-33 > URL: https://issues.jboss.org/browse/HAWKULARQE-33 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Vojtech Prusa > Priority: Critical > > See [JMAN4-188|https://issues.jboss.org/browse/JMAN4-188] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8166) The enable-elytron.cli script doesn't change configuration of messaging subsystem

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8166: --------------------------------- Summary: The enable-elytron.cli script doesn't change configuration of messaging subsystem Key: WFLY-8166 URL: https://issues.jboss.org/browse/WFLY-8166 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Josef Cacek Reconfiguration of the {{standalone-full.xml}} profile in {{testsuite/shared/enable-elytron.cli}} should change the messaging subsystem configuration too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-969) Add a KeyStore implementation that can use the key store password for retrieving entries.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-969?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-969: -------------------------------------- No a key-store resource needs to return a KeyStore instance, it can't return a KeyManager instance. Some resources do make use of the raw KeyStore. > Add a KeyStore implementation that can use the key store password for retrieving entries. > ----------------------------------------------------------------------------------------- > > Key: ELY-969 > URL: https://issues.jboss.org/browse/ELY-969 > Project: WildFly Elytron > Issue Type: Feature Request > Components: KeyStores > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta28 > > > A KeyManager which uses a KeyStore is defined independently of the KeyStore - it is the KeyManager that has the password for the entry in the KeyStore whilst the KeyStore has the password for the overall store. > In many cases the password used for the overall store is the same password as used for the entries. > We should provide a KeyStore implementation that can substitute the password received. > We may even be able to go one step further and add a password resolver which could mean a CredentialStore is used to obtain the password for different entries, -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-969) Add a KeyStore implementation that can use the key store password for retrieving entries.

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-969?page=com.atlassian.jira.plugin.sy... ] Martin Choma commented on ELY-969: ---------------------------------- Cool! But it seems to me moving key password(s) into KeyStore, makes key-manager resource more pointless. As key-manager is in real used only 1 (however array is prepared), could be IMO moved into key-store resource (with only valid attribute algorithm). > Add a KeyStore implementation that can use the key store password for retrieving entries. > ----------------------------------------------------------------------------------------- > > Key: ELY-969 > URL: https://issues.jboss.org/browse/ELY-969 > Project: WildFly Elytron > Issue Type: Feature Request > Components: KeyStores > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta28 > > > A KeyManager which uses a KeyStore is defined independently of the KeyStore - it is the KeyManager that has the password for the entry in the KeyStore whilst the KeyStore has the password for the overall store. > In many cases the password used for the overall store is the same password as used for the entries. > We should provide a KeyStore implementation that can substitute the password received. > We may even be able to go one step further and add a password resolver which could mean a CredentialStore is used to obtain the password for different entries, -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8165) Missing log that authetication failed in Elytron LdapRealm

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-8165: ---------------------------------- Summary: Missing log that authetication failed in Elytron LdapRealm Key: WFLY-8165 URL: https://issues.jboss.org/browse/WFLY-8165 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse In case when wrong password is passed during authentication through LdapRealm then server log does not include information that 'authentication failed'. Following log occurs in server.log: {code} 2017-02-20 13:16:41,482 DEBUG [org.wildfly.security] (default task-2) Trying to create identity for principal [jduke]. 2017-02-20 13:16:41,483 DEBUG [org.wildfly.security] (default task-2) Executing search [(uid={0})] in context [ou=People,dc=jboss,dc=org] with arguments [[Ljava.lang.String;@3e8a4972]. Returning attributes are [[userPassword]]. Binary attributes are [[]]. 2017-02-20 13:16:41,491 DEBUG [org.wildfly.security] (default task-2) Found entry [uid=jduke,ou=People,dc=jboss,dc=org]. 2017-02-20 13:16:41,493 DEBUG [org.wildfly.security] (default task-2) Identity for principal [jduke] found at [uid=jduke,ou=People,dc=jboss,dc=org]. 2017-02-20 13:16:41,504 DEBUG [org.wildfly.security] (default task-2) Context [javax.naming.ldap.InitialLdapContext@3db0aa06] was closed. Connection closed or just returned to the pool. 2017-02-20 13:16:41,506 DEBUG [org.wildfly.security] (default task-2) User jduke authorization failed. 2017-02-20 13:16:41,506 TRACE [org.wildfly.security] (default task-2) Handling AuthenticationCompleteCallback: fail {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8141) CachedConnectionManager add operation excepts no parameters anymore

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-8141?page=com.atlassian.jira.plugin.... ] Ingo Weiss commented on WFLY-8141: ---------------------------------- Hi [~brian.stansberry], then 1) would transform CCM into a regular node which, I believe, wasn't the original intention. Wouldn't it be better, in that case, to return the add op and make it an noop? > CachedConnectionManager add operation excepts no parameters anymore > ------------------------------------------------------------------- > > Key: WFLY-8141 > URL: https://issues.jboss.org/browse/WFLY-8141 > Project: WildFly > Issue Type: Bug > Components: Domain Management, JCA > Affects Versions: 11.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Ingo Weiss > Priority: Critical > > Fix for WFLY-2640 broke :add operation for cached-connection-manager > scipts that do > {noformat} > /profile=default-web/subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true") > {noformat} > {noformat} > /subsystem=jca/cached-connection-manager=cached-connection-manager:add(install="true") > {noformat} > now fail with > {{Operation 'add' does not expect any property.}} > This breaks our quickstarts -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-43) Hawkular Agent for EAP 6.4

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-43?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-43: ------------------------------------- Description: Smoke test based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... > Hawkular Agent for EAP 6.4 > -------------------------- > > Key: HAWKULARQE-43 > URL: https://issues.jboss.org/browse/HAWKULARQE-43 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > Smoke test based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-43) Hawkular Agent for EAP 6.4

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-43: ---------------------------------------- Summary: Hawkular Agent for EAP 6.4 Key: HAWKULARQE-43 URL: https://issues.jboss.org/browse/HAWKULARQE-43 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-880) Unable to set IPv6 address in Elytron authentication context match-host rule

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/ELY-880?page=com.atlassian.jira.plugin.sy... ] Tomas Hofman updated ELY-880: ----------------------------- Original Estimate: 3 days Remaining Estimate: 3 days > Unable to set IPv6 address in Elytron authentication context match-host rule > ---------------------------------------------------------------------------- > > Key: ELY-880 > URL: https://issues.jboss.org/browse/ELY-880 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Affects Versions: 1.1.0.Beta18 > Reporter: Martin Choma > Assignee: Tomas Hofman > Original Estimate: 3 days > Remaining Estimate: 3 days > > Setting IPv6 address in wildfly-config.xml cause validation error. > {code:xml|title=wildfly-config.xml} > <?xml version="1.0" encoding="UTF-8"?> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-configurations> > <configuration name="set-host-to-localhost"> > <set-host name="localhost"/> > </configuration> > </authentication-configurations> > <authentication-rules> > <rule use-configuration="set-host-to-localhost"> > <match-host name="::1"/> > </rule> > </authentication-rules> > </authentication-client> > {code} > {code:title=server.log} > java.lang.IllegalArgumentException: ELY01029: Invalid host specification "::1" > at org.wildfly.security.auth.client.MatchHostRule.<init>(MatchHostRule.java:39) > at org.wildfly.security.auth.client.MatchRule.matchHost(MatchRule.java:411) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAbstractMatchRuleType(ElytronXmlParser.java:701) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationRuleType(ElytronXmlParser.java:467) > at org.wildfly.security.auth.client.ElytronXmlParser.parseRulesType(ElytronXmlParser.java:484) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:241) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:169) > at org.wildfly.security.auth.client.XmlConfigurationTest.testMatcHostRuleConfiguration(XmlConfigurationTest.java:175) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > {code} > It is because of elytron validation [1]. However don't know if just allowing ":" in regexp is valid solution. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/7debbcabc7c20be5... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017