July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-131) Add format characters for module name, module version

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-131?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-131: --------------------------------- Fix Version/s: 2.1.0.Alpha3 (was: 2.1.0.Alpha2) > Add format characters for module name, module version > ----------------------------------------------------- > > Key: LOGMGR-131 > URL: https://issues.jboss.org/browse/LOGMGR-131 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha3 > > > In JDK9, StackTraceElements contain moduleName and moduleVersion fields. This information is useful for debugging purposes, thus format characters should be allocated towards these values. Ideally it'll be something non-conflicting with respect to log4j and other common ancestor/related frameworks, but that is less important than the basic support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-130) JDK9 Support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-130?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-130: --------------------------------- Fix Version/s: 2.1.0.Alpha3 (was: 2.1.0.Alpha2) > JDK9 Support > ------------ > > Key: LOGMGR-130 > URL: https://issues.jboss.org/browse/LOGMGR-130 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: David Lloyd > Fix For: 2.1.0.Alpha3 > > > A few enhancements become possible, desirable, and/or necessary when moving to JDK 9. This is an umbrella parent issue to cover them all. > Note that some of these features may require multi-version JAR building, which Maven cannot yet do. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-113) Create a better way to handle a TCP reconnect policy

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-113?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-113: --------------------------------- Fix Version/s: 2.1.0.Alpha3 (was: 2.1.0.Alpha2) > Create a better way to handle a TCP reconnect policy > ---------------------------------------------------- > > Key: LOGMGR-113 > URL: https://issues.jboss.org/browse/LOGMGR-113 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Perkins > Fix For: 2.1.0.Alpha3 > > > The audit logger in WildFly uses it's own policy to reconnect a TCP connection for the {{SyslogHandler}}. The current {{org.jboss.logmanager.handlers.TcpOutputStream}} handles a reconnection on it's own unless a deprecated constructor is used. A way to set some kind of policy or enable the reconnection to be turned off should be added. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-86) Create an exception filter

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-86?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-86: -------------------------------- Fix Version/s: 2.1.0.Alpha3 (was: 2.1.0.Alpha2) > Create an exception filter > -------------------------- > > Key: LOGMGR-86 > URL: https://issues.jboss.org/browse/LOGMGR-86 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Fix For: 2.1.0.Alpha3 > > > For now this is just a thought so that users can filter messages based on an exception in the stack trace. Currently it's not possible to use a regex filter as the stack trace is not used in when testing for matches and it probably shouldn't be used. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-52) Add option to WriterHandler to collapse repeated messages

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-52?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-52: -------------------------------- Fix Version/s: 2.1.0.Alpha3 (was: 2.1.0.Alpha2) > Add option to WriterHandler to collapse repeated messages > --------------------------------------------------------- > > Key: LOGMGR-52 > URL: https://issues.jboss.org/browse/LOGMGR-52 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 2.1.0.Alpha3 > > > The WriterHandler could have a time interval configured wherein a repeated message would be collapsed. > The last message would be stored in a field for comparison along with a nanoTime tag (the timestamp on the message is not adequate because the clock can have skew or be reset completely at any time). If the current message string equals the last message string, and collapsing is enabled, then instead of logging the message, a count is incremented. If the current message is not equal, then the stored message is logged with a tag indicating the number of repeats (i18n?) and then the next submitted message is logged. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6534) LdapExtLoginModule authentication fails when some part of DN is part of LDAP URL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6534?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-6534. ------------------------------------ Resolution: Won't Fix > LdapExtLoginModule authentication fails when some part of DN is part of LDAP URL > -------------------------------------------------------------------------------- > > Key: WFLY-6534 > URL: https://issues.jboss.org/browse/WFLY-6534 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > > In case when part of DN is placed in LDAP URL instead of baseCtxDN then authentication fails (see [1] for details about this URL) in LdapExtLoginModule. Authentication is provided by binding with user DN and password, but in this case user DN does not include DN part from LDAP URL which leads to fail. > Thrown exception: > {code} > javax.naming.AuthenticationException: LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=jduke,ou=People > com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3135) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3081) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) > com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) > com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) > com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) > com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) > org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114) > org.jboss.as.naming.InitialContext.init(InitialContext.java:99) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89) > org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43) > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) > javax.naming.InitialContext.init(InitialContext.java:244) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.security.auth.spi.LdapExtLoginModule.constructInitialLdapContext(LdapExtLoginModule.java:836) > org.jboss.security.auth.spi.LdapExtLoginModule.bindDNAuthentication(LdapExtLoginModule.java:565) > org.jboss.security.auth.spi.LdapExtLoginModule.createLdapInitContext(LdapExtLoginModule.java:465) > org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:343) > org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ... > {code} > [1] https://tools.ietf.org/html/rfc2255 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-154) Log rotations should be more resilient to failed rotations

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-154?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-154: --------------------------------- Fix Version/s: 2.0.8.Final (was: 2.0.7.Final) > Log rotations should be more resilient to failed rotations > ---------------------------------------------------------- > > Key: LOGMGR-154 > URL: https://issues.jboss.org/browse/LOGMGR-154 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Priority: Critical > Fix For: 2.0.8.Final, 2.1.0.Alpha3 > > > If a failure occurs while rotating a file the file handler will stop working. The file handler should instead report the failed rotation, but keep allowing messages to be written. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6535) LdapLoginModule authentication fails when some part of DN is part of LDAP URL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6535?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6535: -------------------------------------- Assignee: (was: Darran Lofthouse) > LdapLoginModule authentication fails when some part of DN is part of LDAP URL > ----------------------------------------------------------------------------- > > Key: WFLY-6535 > URL: https://issues.jboss.org/browse/WFLY-6535 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > > In case when part of DN is placed in LDAP URL instead of principalDNSuffix then authentication fails (see [1] for details about this URL) in LdapLoginModule. Authentication is provided by binding with user DN and password, but in this case user DN does not include DN part from LDAP URL which leads to fail. > Thrown exception: > {code} > javax.naming.AuthenticationException: LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=jduke,ou=People > com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3135) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3081) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) > com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) > com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) > com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) > com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) > org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114) > org.jboss.as.naming.InitialContext.init(InitialContext.java:99) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89) > org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43) > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) > javax.naming.InitialContext.init(InitialContext.java:244) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.security.auth.spi.LdapLoginModule.createLdapInitContext(LdapLoginModule.java:362) > org.jboss.security.auth.spi.LdapLoginModule.validatePassword(LdapLoginModule.java:289) > org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ... > {code} > [1] https://tools.ietf.org/html/rfc2255 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6534) LdapExtLoginModule authentication fails when some part of DN is part of LDAP URL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6534?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-6534: -------------------------------------- Assignee: (was: Darran Lofthouse) > LdapExtLoginModule authentication fails when some part of DN is part of LDAP URL > -------------------------------------------------------------------------------- > > Key: WFLY-6534 > URL: https://issues.jboss.org/browse/WFLY-6534 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > > In case when part of DN is placed in LDAP URL instead of baseCtxDN then authentication fails (see [1] for details about this URL) in LdapExtLoginModule. Authentication is provided by binding with user DN and password, but in this case user DN does not include DN part from LDAP URL which leads to fail. > Thrown exception: > {code} > javax.naming.AuthenticationException: LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=jduke,ou=People > com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3135) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3081) > com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) > com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) > com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) > com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) > com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) > com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) > org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114) > org.jboss.as.naming.InitialContext.init(InitialContext.java:99) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89) > org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43) > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) > javax.naming.InitialContext.init(InitialContext.java:244) > javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > org.jboss.security.auth.spi.LdapExtLoginModule.constructInitialLdapContext(LdapExtLoginModule.java:836) > org.jboss.security.auth.spi.LdapExtLoginModule.bindDNAuthentication(LdapExtLoginModule.java:565) > org.jboss.security.auth.spi.LdapExtLoginModule.createLdapInitContext(LdapExtLoginModule.java:465) > org.jboss.security.auth.spi.LdapExtLoginModule.validatePassword(LdapExtLoginModule.java:343) > org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:283) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ... > {code} > [1] https://tools.ietf.org/html/rfc2255 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-154) Log rotations should be more resilient to failed rotations

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-154?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-154: --------------------------------- Fix Version/s: 2.1.0.Alpha3 (was: 2.1.0.Alpha2) > Log rotations should be more resilient to failed rotations > ---------------------------------------------------------- > > Key: LOGMGR-154 > URL: https://issues.jboss.org/browse/LOGMGR-154 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Priority: Critical > Fix For: 2.0.8.Final, 2.1.0.Alpha3 > > > If a failure occurs while rotating a file the file handler will stop working. The file handler should instead report the failed rotation, but keep allowing messages to be written. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 July 2017