August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9166) Fix OtpSaslTestCase to reflect OTP related changes in model

by Josef Cacek (JIRA)

Josef Cacek created WFLY-9166: --------------------------------- Summary: Fix OtpSaslTestCase to reflect OTP related changes in model Key: WFLY-9166 URL: https://issues.jboss.org/browse/WFLY-9166 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Josef Cacek Follow up to JBEAP-12140. The {{OtpSaslTestCase}} has to be updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1316) Elytron - unable to use OTP SASL mechanism

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-1316?page=com.atlassian.jira.plugin.s... ] Josef Cacek moved WFCORE-3045 to ELY-1316: ------------------------------------------ Project: WildFly Elytron (was: WildFly Core) Key: ELY-1316 (was: WFCORE-3045) Component/s: SASL (was: Security) > Elytron - unable to use OTP SASL mechanism > ------------------------------------------ > > Key: ELY-1316 > URL: https://issues.jboss.org/browse/ELY-1316 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Labels: eap7.1-rfe-failure > > I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). > It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1316) Elytron - unable to use OTP SASL mechanism

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-1316?page=com.atlassian.jira.plugin.s... ] Josef Cacek reassigned ELY-1316: -------------------------------- Assignee: Josef Cacek (was: Darran Lofthouse) > Elytron - unable to use OTP SASL mechanism > ------------------------------------------ > > Key: ELY-1316 > URL: https://issues.jboss.org/browse/ELY-1316 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: Josef Cacek > Assignee: Josef Cacek > Labels: eap7.1-rfe-failure > > I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). > It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3136) Add Generic type CLI commands into docs (CLI guide)

by Vikas Dadhich (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3136?page=com.atlassian.jira.plugi... ] Vikas Dadhich updated WFCORE-3136: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2684 > Add Generic type CLI commands into docs (CLI guide) > --------------------------------------------------- > > Key: WFCORE-3136 > URL: https://issues.jboss.org/browse/WFCORE-3136 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vikas Dadhich > > Documentation for generic type CLI commands is missing. > references > - https://developer.jboss.org/wiki/GenericTypeCLICommands > - https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/resource... > Related issue: https://issues.jboss.org/browse/JBEAP-5042 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3136) Add Generic type CLI commands into docs (CLI guide)

by Vikas Dadhich (JIRA)

Vikas Dadhich created WFCORE-3136: ------------------------------------- Summary: Add Generic type CLI commands into docs (CLI guide) Key: WFCORE-3136 URL: https://issues.jboss.org/browse/WFCORE-3136 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Vikas Dadhich Documentation for generic type CLI commands is missing. references - https://developer.jboss.org/wiki/GenericTypeCLICommands - https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/resource... Related issue: https://issues.jboss.org/browse/JBEAP-5042 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2031) GMS: replace ViewHandler.queue with BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2031?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2031: -------------------------------- Multiple join and merge requests are handled correctly, but multiple suspect events not - they are handled one-by-one. The culprit is Event.SUSPECT which takes as arg a single suspected member. Need to change this into a list of suspected members. > GMS: replace ViewHandler.queue with BlockingQueue > ------------------------------------------------- > > Key: JGRP-2031 > URL: https://issues.jboss.org/browse/JGRP-2031 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.5 > > > Replace {{GMS$ViewHandler.Queue}} with {{LinkedBlockingQueue}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

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

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9161?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9161: ------------------------------------- This looks like an Elytron issue. [~dlofthouse] any thoughts on this? > 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: James Perkins > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2031) GMS: replace ViewHandler.queue with BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2031?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2031: -------------------------------- It seems we don't need {{ViewHandler}} to start a thread to process requests; all requests (join, leave, merge, join-with-state and suspect) can be handled from the thread which submitted the request/event. > GMS: replace ViewHandler.queue with BlockingQueue > ------------------------------------------------- > > Key: JGRP-2031 > URL: https://issues.jboss.org/browse/JGRP-2031 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.5 > > > Replace {{GMS$ViewHandler.Queue}} with {{LinkedBlockingQueue}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9165) TransactionScopedJMSContextTestCase fails with security manager

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-9165: ---------------------------------- Summary: TransactionScopedJMSContextTestCase fails with security manager Key: WFLY-9165 URL: https://issues.jboss.org/browse/WFLY-9165 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Hynek Švábek TransactionScopedJMSContextTestCase fails with security manager {code} Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.wildfly.security.permission.ElytronPermission" "getSecurityDomain")" in code source "(vfs:/content/TransactionScopedJMSContextTestCase.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.TransactionScopedJMSContextTestCase.jar" 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 org.wildfly.security.auth.server.SecurityDomain.getCurrent(SecurityDomain.java:160) at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory.createThread(ElytronManagedThreadFactory.java:48) at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl.newThread(ManagedThreadFactoryImpl.java:127) at org.jboss.as.test.integration.messaging.jms.context.transactionscoped.auxiliary.ThreadLauncher.start(ThreadLauncher.java:56) 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.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:90) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:57) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:135) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:59) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275) ... 180 more ... {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9164) ResourceAdapterPoolAttributesTestCase fails with security manage

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-9164: ---------------------------------- Summary: ResourceAdapterPoolAttributesTestCase fails with security manage Key: WFLY-9164 URL: https://issues.jboss.org/browse/WFLY-9164 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Hynek Švábek ResourceAdapterPoolAttributesTestCase fails with security manage {code} Caused 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/local8056268563783903312.challenge" "read")" in code source "(vfs:/content/pool-attributes-test.rar/pool-attributes-test.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.pool-attributes-test.rar" 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) ... 162 more ... {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2017