October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1382) Add version 1.0.1 of the Elytron schema

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1382: ------------------------------------- Summary: Add version 1.0.1 of the Elytron schema Key: ELY-1382 URL: https://issues.jboss.org/browse/ELY-1382 Project: WildFly Elytron Issue Type: Task Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.4.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1381) Update KeyStore and SSLContext definitions to use credential store references.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1381?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1381: ---------------------------------- Fix Version/s: 1.1.4.CR1 > Update KeyStore and SSLContext definitions to use credential store references. > ------------------------------------------------------------------------------ > > Key: ELY-1381 > URL: https://issues.jboss.org/browse/ELY-1381 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.4.CR1, 1.2.0.Beta5 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9161) JobControlTestCase fails with security manager

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-9161?page=com.atlassian.jira.plugin.... ] Yeray Borges resolved WFLY-9161. -------------------------------- Fix Version/s: 11.0.0.CR1 Resolution: Cannot Reproduce Bug Issue already solved by WFLY-9208 > JobControlTestCase fails with security manager > ---------------------------------------------- > > Key: WFLY-9161 > URL: https://issues.jboss.org/browse/WFLY-9161 > Project: WildFly > Issue Type: Bug > Components: Batch, Test Suite > Reporter: Hynek Švábek > Assignee: Yeray Borges > Fix For: 11.0.0.CR1 > > > JobControlTestCase fails with security manager > Some tests fail with: > {code} > aused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: > JBOSS-LOCAL-USER: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/hsvabek/securityworkspace/VERIFICATION/2017_08_02_BEAP-7584/jboss-eap-7.1.0.ER3-src/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local2441956400719098652.challenge" "read")" in code source "(vfs:/content/test-batch.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.test-batch.war" from Service Module Loader") > DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication > at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:400) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:571) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:542) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:504) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:492) > at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:194) > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118) > ... 155 more > ... > {code} > or > {code} > Suppressed: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/hsvabek/securityworkspace/VERIFICATION/2017_08_02_BEAP-7584/jboss-eap-7.1.0.ER3-src/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local471205335337215113.challenge" "read")" in code source "(vfs:/content/test-batch.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.test-batch.war" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:350) > at java.io.FileInputStream.<init>(FileInputStream.java:127) > at org.wildfly.security.sasl.localuser.LocalUserClient.evaluateMessage(LocalUserClient.java:93) > at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180) > at org.wildfly.security.sasl.util.AbstractSaslClient.evaluateChallenge(AbstractSaslClient.java:59) > at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55) > at java.security.AccessController.doPrivileged(Native Method) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.lambda$handleEvent$0(ClientConnectionOpenListener.java:644) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:898) > ... 3 more > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1368) Elytron CommandCredentialSource closes STD_ERR stream without consuming it

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1368?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1368: ---------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/989 > Elytron CommandCredentialSource closes STD_ERR stream without consuming it > -------------------------------------------------------------------------- > > Key: ELY-1368 > URL: https://issues.jboss.org/browse/ELY-1368 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Affects Versions: 1.2.0.Beta3 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.3.Final, 1.2.0.Beta4 > > > External commands used for retrieving Elytron credentials may fail due to closed error stream. > The {{CommandCredentialSource}} closes STD_ERR stream without consuming it. > Elytron unit test {{CommandCredentialSourceTest}} (which executes an external java program) hits this issue in some environments. Log contains; > {noformat} > 11:30:29,201 TRACE (main) [org.wildfly.security] <CommandCredentialSource.java:114> Exit code from password command = 141 > {noformat} > The issue was investigated in this PR. You can find more details there: > https://github.com/wildfly-security/wildfly-elytron/pull/981 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-82) PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-82?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-82: -------------------------------- Fix Version/s: 2.1.0.Alpha6 (was: 2.1.0.Alpha5) > PeriodicSizeRotatingFileHandlerTests rotation tests are a bit dodgy > -------------------------------------------------------------------- > > Key: LOGMGR-82 > URL: https://issues.jboss.org/browse/LOGMGR-82 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.1.0.Alpha6 > > > The rotation tests seem to fail at random days and times. The test {{testPeriodicAndSizeRotate}} needs to be looked at before re-enabling it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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.Alpha6 (was: 2.1.0.Alpha5) > 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.Alpha6 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-134) Add module name, module version fields to ExtLogRecord

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-134?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-134: --------------------------------- Fix Version/s: 2.1.0.Alpha6 (was: 2.1.0.Alpha5) > Add module name, module version fields to ExtLogRecord > ------------------------------------------------------ > > Key: LOGMGR-134 > URL: https://issues.jboss.org/browse/LOGMGR-134 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha6 > > > It will be necessary for ExtLogRecord to carry additional fields for Java 9 module name and module version. The serialization impact should be analyzed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-133) Use StackWalker to get extended log record information

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-133?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-133: --------------------------------- Fix Version/s: 2.1.0.Alpha6 (was: 2.1.0.Alpha5) > Use StackWalker to get extended log record information > ------------------------------------------------------ > > Key: LOGMGR-133 > URL: https://issues.jboss.org/browse/LOGMGR-133 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha6 > > > Under Java 9, you can use a StackWalker to efficiently traverse the stack and return information about callers. Using this mechanism should be substantially better-performing than snapshotting the stack to acquire the calling class information for the extended log record class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-132) Remove extended stack trace functionality

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-132?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-132: --------------------------------- Fix Version/s: 2.1.0.Alpha6 (was: 2.1.0.Alpha5) > Remove extended stack trace functionality > ----------------------------------------- > > Key: LOGMGR-132 > URL: https://issues.jboss.org/browse/LOGMGR-132 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha6 > > > Java 9 stack traces include module name and version number. All our extended stack trace hacky code should be deleted and both format characters should yield a standard stack trace under Java 9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[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.Alpha6 (was: 2.1.0.Alpha5) > 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.Alpha6 > > > 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, 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 October 2017