[JBoss JIRA] (WFLY-7888) Some tests using TimeoutUtil fail with security manager
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-7888?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka reassigned WFLY-7888:
-------------------------------------
Assignee: Ondra Chaloupka (was: Ingo Weiss)
> Some tests using TimeoutUtil fail with security manager
> -------------------------------------------------------
>
> Key: WFLY-7888
> URL: https://issues.jboss.org/browse/WFLY-7888
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Jan Tymel
> Assignee: Ondra Chaloupka
>
> *org.jboss.as.test.iiop.transaction.timeout.IIOPTimeoutTestCase#noTimeoutStateful*
> *org.jboss.as.test.iiop.transaction.timeout.IIOPTimeoutTestCase#noTimeoutStateless*
> *org.jboss.as.test.iiop.transaction.timeout.IIOPTimeoutTestCase#timeoutStateful*
> *org.jboss.as.test.iiop.transaction.timeout.IIOPTimeoutTestCase#timeoutStateless*
> {{./integration-tests.sh -DtestLogToFile -Dts.noSmoke -Dts.iiop -Dtest=IIOPTimeoutTestCase -Dsecurity.manager}}
> {code}
> ERROR [org.jboss.as.ejb3.invocation] (p: default-threadpool; w: Idle) WFLYEJB0034: EJB Invocation failed on component StatelessBean for method public abstract void org.jboss.as.test.iiop.transaction.timeout.TestBeanRemote.testTransaction() throws java.rmi.RemoteException: javax.ejb.EJBException: WFLYEJB0442: Unexpected Error
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:184)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:456)
> at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:84)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:44)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:75)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:375)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:375)
> at java.security.AccessController.doPrivileged(AccessController.java:686)
> at java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:742)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:75)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.jboss.as.ejb3.iiop.EjbCorbaServant._invoke(EjbCorbaServant.java:328)
> at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:654)
> at com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:205)
> at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1700)
> at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1558)
> at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:940)
> at com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:198)
> at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:712)
> at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:471)
> at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1230)
> at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:490)
> at com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:519)
> Caused by: java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.ensureError(J9VMInternals.java:141)
> at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:130)
> at org.jboss.as.test.integration.transactions.TxTestUtil.<clinit>(TxTestUtil.java:42)
> at org.jboss.as.test.iiop.transaction.timeout.StatelessBean.testTransaction(StatelessBean.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:456)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:85)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:96)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> ... 54 more
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "ts.timeout.factor" "read")" in code source "(vfs:/content/stateless-iiop-txn-timeout.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.stateless-iiop-txn-timeout.jar:main" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:469)
> at java.lang.System.getProperty(System.java:443)
> at java.lang.System.getProperty(System.java:427)
> at java.lang.Integer.getInteger(Integer.java:1113)
> at java.lang.Integer.getInteger(Integer.java:1069)
> at org.jboss.as.test.shared.TimeoutUtil.<clinit>(TimeoutUtil.java:39)
> ... 81 more
> {code}
> *org.jboss.as.test.integration.jca.statistics.xa.XaDataSourcePoolStatisticsTestCase#testXACommit*
> *org.jboss.as.test.integration.jca.statistics.xa.XaDataSourcePoolStatisticsTestCase#testXARollback*
> {{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=XaDataSourcePoolStatisticsTestCase -Dsecurity.manager}}
> {code}
> ERROR [org.jboss.as.ejb3.invocation] (default task-5) WFLYEJB0034: EJB Invocation failed on component SLSB1 for method public abstract void org.jboss.as.test.integration.jca.statistics.xa.SLSB.commit() throws java.lang.Exception: javax.ejb.EJBException: WFLYEJB0443: EJB 3.1 FR 13.3.3: BMT bean SLSB1 should complete transaction before returning.
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:86)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:106)
> at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:456)
> at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:84)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:375)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:375)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:568)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:75)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:340)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:68)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202)
> at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.processMessage(MethodInvocationMessageHandler.java:268)
> at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.processMessage(VersionOneProtocolChannelReceiver.java:213)
> at org.jboss.as.ejb3.remote.protocol.versiontwo.VersionTwoProtocolChannelReceiver.processMessage(VersionTwoProtocolChannelReceiver.java:76)
> at org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver.handleMessage(VersionOneProtocolChannelReceiver.java:159)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:434)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:789)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
> ... 62 more
> Caused by: java.lang.ExceptionInInitializerError
> at org.jboss.as.test.integration.transactions.TxTestUtil.<clinit>(TxTestUtil.java:42)
> at org.jboss.as.test.integration.jca.statistics.xa.SLSB1.commit(SLSB1.java:54)
> 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:498)
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:456)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:85)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:96)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:359)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103)
> ... 60 more
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.util.PropertyPermission" "ts.timeout.factor" "read")" in code source "(vfs:/content/xa-datasource-pool-statistics-test.ear/xa_transactions.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.xa-datasource-pool-statistics-test.ear.xa_transactions.jar:main" from Service Module Loader")
> at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278)
> at org.wildfly.security.manager.WildFlySecurityManager.checkPropertyAccess(WildFlySecurityManager.java:469)
> at java.lang.System.getProperty(System.java:717)
> at java.lang.Integer.getInteger(Integer.java:1101)
> at java.lang.Integer.getInteger(Integer.java:1057)
> at org.jboss.as.test.shared.TimeoutUtil.<clinit>(TimeoutUtil.java:39)
> ... 78 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-1958) Clean up testsuite Elytron registration
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1958?page=com.atlassian.jira.plugi... ]
Kabir Khan reopened WFCORE-1958:
--------------------------------
Reopening after speaking to Brian, there is one remaining affected test
> Clean up testsuite Elytron registration
> ---------------------------------------
>
> Key: WFCORE-1958
> URL: https://issues.jboss.org/browse/WFCORE-1958
> Project: WildFly Core
> Issue Type: Task
> Components: Test Suite
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta6
>
>
> In a couple of places we have artificially registered the WildFly Elytron Security provider, we need to address this so tests can automatically have it available to them..
> Also re-enable the following test case: -
> * org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JGRP-2159) Delta view cannot be installed
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2159?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2159:
--------------------------------
Unit test now reproduces the issue.
Reusing {{Event.GET_CURRENT_VIEW}} to ask the sender of an incompatible delta view for a full view.
> Delta view cannot be installed
> ------------------------------
>
> Key: JGRP-2159
> URL: https://issues.jboss.org/browse/JGRP-2159
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.1, 4.0.1
>
> Attachments: discarded_delta_view.log
>
>
> A DeltaView cannot be installed because the ref view-id is not the current view-id.
> Looking at the view sequence for members J, K and L:
> {noformat}
> 19:22:54,278 DEBUG (testng-Test:[]) [GMS] J: installing view [J|0] (1) [J]
> 19:22:56,519 DEBUG (testng-Test:[]) [GMS] K: installing view [J|1] (2) [J, K]
> 19:22:56,572 DEBUG (jgroups-7,J:[]) [GMS] J: installing view [J|1] (2) [J, K]
> 19:22:56,590 DEBUG (jgroups-5,K:[]) [GMS] K: installing view [J|2] (2) [J, K]
> 19:22:58,585 DEBUG (jgroups-5,J:[]) [GMS] J: installing view [J|3] (3) [J, K, L]
> 19:23:00,603 DEBUG (testng-Test:[]) [GMS] L: installing view [J|3] (3) [J, K, L]
> {noformat}
> K cannot install DeltaView J|3 because it has view J|2 but the DeltaView has ref view-id J|1.
> The reason is that J|2 was apparently installed *only* at K (but not at coordinator J1!), despite it being the same view as J|1.
> We need to look into why J|2 was installed at K only. Second line of defense: when a DeltaView cannot be installed, send a message to the view sender (coord) and solicit the full view instead.
> See the attached log.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8238) Unable to undefine credential-reference
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-8238?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFLY-8238:
------------------------------------
[~thofman], thank you :)
> Unable to undefine credential-reference
> ---------------------------------------
>
> Key: WFLY-8238
> URL: https://issues.jboss.org/browse/WFLY-8238
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Reporter: Claudio Miranda
> Assignee: Tomas Hofman
>
> A bridge is added and a credential-reference is set.
> However a "password" attribute cannot be set as the alternatives constraint validates the data, but the password attribute has a default value.
> Also neither credential-reference and password are required=true, so they may be undefined.
> {code}
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ)
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1})
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the resource does not define any alternative to this attribute."},
> "rolled-back" => true
> }
> {code}
> The same problem, when user adds a bridge with a password and later wants to undefine it to add a credential-reference
> {code}
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ,password=senha1)
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=password)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (password) can not been undefined as the resource does not define any alternative to this attribute."},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8255) New EJB Authentication tests (in AS TS) fail with Elytron profile
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/WFLY-8255?page=com.atlassian.jira.plugin.... ]
Josef Cacek reassigned WFLY-8255:
---------------------------------
Assignee: Jan Kalina (was: Darran Lofthouse)
> New EJB Authentication tests (in AS TS) fail with Elytron profile
> -----------------------------------------------------------------
>
> Key: WFLY-8255
> URL: https://issues.jboss.org/browse/WFLY-8255
> Project: WildFly
> Issue Type: Bug
> Components: Security, Test Suite
> Reporter: Josef Cacek
> Assignee: Jan Kalina
> Priority: Critical
>
> The newly introduced authentication tests ({{AuthenticationElytronTestCase}}, {{AuthenticationTestCase}}) in {{org.jboss.as.test.integration.ejb.security}} package fail when executed with Elytron AS TS profile.
> {noformat}
> cd testsuite/integration/basic
> mvn clean test -Dtest=org.jboss.as.test.integration.ejb.security.Authentication\* -Delytron
> ...
> Failed tests:
> AuthenticationElytronTestCase.testAuthenticatedCall:15->AbstractAuthenticationTestCase.testAuthenticatedCall:206 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication:15->AbstractAuthenticationTestCase.testAuthentication:136 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication_BadPwd:15->AbstractAuthenticationTestCase.testAuthentication_BadPwd:148 Expected EJBAccessException due to bad password not thrown. (EJB 3.1 FR 17.6.9)
> AuthenticationElytronTestCase.testAuthentication_TwoBeans:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans:161 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth:174 expected:<[user1]> but was:<[anonymous]>
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd:188 Expected EJBAccessException due to bad password not thrown. (EJB 3.1 FR 17.6.9)
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:262 null
> AuthenticationElytronTestCase.testICIRSingle:15->AbstractAuthenticationTestCase.testICIRSingle:275 null
> AuthenticationElytronTestCase.testICIR_TwoBeans:15->AbstractAuthenticationTestCase.testICIR_TwoBeans:290 null
> AuthenticationElytronTestCase.testICIR_TwoBeans_ReAuth:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth:312 null
> AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:262 null
> Tests in error:
> AuthenticationElytronTestCase.testAuthentication_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:240->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:252->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testAuthentication_TwoBeans_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:246->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testAuthentication_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_ViaServlet:234->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_ReAuth_ViaServlet:417->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:437->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_TwoBeans_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ViaServlet:427->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationElytronTestCase.testICIR_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_ViaServlet:407->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:240->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:252->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:246->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testAuthentication_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_ViaServlet:234->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_ReAuth_ViaServlet:417->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:437->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_TwoBeans_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_TwoBeans_ViaServlet:427->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> AuthenticationTestCase.testICIR_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_ViaServlet:407->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
> Tests run: 38, Failures: 11, Errors: 16, Skipped: 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8255) New EJB Authentication tests (in AS TS) fail with Elytron profile
by Josef Cacek (JIRA)
Josef Cacek created WFLY-8255:
---------------------------------
Summary: New EJB Authentication tests (in AS TS) fail with Elytron profile
Key: WFLY-8255
URL: https://issues.jboss.org/browse/WFLY-8255
Project: WildFly
Issue Type: Bug
Components: Test Suite, Security
Reporter: Josef Cacek
Assignee: Darran Lofthouse
Priority: Critical
The newly introduced authentication tests ({{AuthenticationElytronTestCase}}, {{AuthenticationTestCase}}) in {{org.jboss.as.test.integration.ejb.security}} package fail when executed with Elytron AS TS profile.
{noformat}
cd testsuite/integration/basic
mvn clean test -Dtest=org.jboss.as.test.integration.ejb.security.Authentication\* -Delytron
...
Failed tests:
AuthenticationElytronTestCase.testAuthenticatedCall:15->AbstractAuthenticationTestCase.testAuthenticatedCall:206 expected:<[user1]> but was:<[anonymous]>
AuthenticationElytronTestCase.testAuthentication:15->AbstractAuthenticationTestCase.testAuthentication:136 expected:<[user1]> but was:<[anonymous]>
AuthenticationElytronTestCase.testAuthentication_BadPwd:15->AbstractAuthenticationTestCase.testAuthentication_BadPwd:148 Expected EJBAccessException due to bad password not thrown. (EJB 3.1 FR 17.6.9)
AuthenticationElytronTestCase.testAuthentication_TwoBeans:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans:161 expected:<[user1]> but was:<[anonymous]>
AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth:174 expected:<[user1]> but was:<[anonymous]>
AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_BadPwd:188 Expected EJBAccessException due to bad password not thrown. (EJB 3.1 FR 17.6.9)
AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:262 null
AuthenticationElytronTestCase.testICIRSingle:15->AbstractAuthenticationTestCase.testICIRSingle:275 null
AuthenticationElytronTestCase.testICIR_TwoBeans:15->AbstractAuthenticationTestCase.testICIR_TwoBeans:290 null
AuthenticationElytronTestCase.testICIR_TwoBeans_ReAuth:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth:312 null
AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth__BadPwd_ViaServlet:262 null
Tests in error:
AuthenticationElytronTestCase.testAuthentication_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:240->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationElytronTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:252->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationElytronTestCase.testAuthentication_TwoBeans_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:246->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationElytronTestCase.testAuthentication_ViaServlet:15->AbstractAuthenticationTestCase.testAuthentication_ViaServlet:234->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationElytronTestCase.testICIR_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_ReAuth_ViaServlet:417->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationElytronTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:437->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationElytronTestCase.testICIR_TwoBeans_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_TwoBeans_ViaServlet:427->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationElytronTestCase.testICIR_ViaServlet:15->AbstractAuthenticationTestCase.testICIR_ViaServlet:407->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_ReAuth_ViaServlet:240->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ReAuth_ViaServlet:252->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_TwoBeans_ViaServlet:246->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testAuthentication_ViaServlet:11->AbstractAuthenticationTestCase.testAuthentication_ViaServlet:234->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testICIR_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_ReAuth_ViaServlet:417->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_TwoBeans_ReAuth_ViaServlet:437->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testICIR_TwoBeans_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_TwoBeans_ViaServlet:427->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
AuthenticationTestCase.testICIR_ViaServlet:11->AbstractAuthenticationTestCase.testICIR_ViaServlet:407->AbstractAuthenticationTestCase.getWhoAmI:359->AbstractAuthenticationTestCase.get:377->AbstractAuthenticationTestCase.execute:393 » IO
Tests run: 38, Failures: 11, Errors: 16, Skipped: 0
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8238) Unable to undefine credential-reference
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFLY-8238?page=com.atlassian.jira.plugin.... ]
Tomas Hofman commented on WFLY-8238:
------------------------------------
[~mchoma] sure I can.
> Unable to undefine credential-reference
> ---------------------------------------
>
> Key: WFLY-8238
> URL: https://issues.jboss.org/browse/WFLY-8238
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Security
> Reporter: Claudio Miranda
> Assignee: Tomas Hofman
>
> A bridge is added and a credential-reference is set.
> However a "password" attribute cannot be set as the alternatives constraint validates the data, but the password attribute has a default value.
> Also neither credential-reference and password are required=true, so they may be undefined.
> {code}
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ)
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1})
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the resource does not define any alternative to this attribute."},
> "rolled-back" => true
> }
> {code}
> The same problem, when user adds a bridge with a password and later wants to undefine it to add a credential-reference
> {code}
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ,password=senha1)
> /profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=password)
> {
> "outcome" => "failed",
> "failure-description" => {"domain-failure-description" => "WFLYMSGAMQ0069: Attribute (password) can not been undefined as the resource does not define any alternative to this attribute."},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8254) Changing sasl-authentication-factory in management interface ends in reload-required state
by Martin Choma (JIRA)
Martin Choma created WFLY-8254:
----------------------------------
Summary: Changing sasl-authentication-factory in management interface ends in reload-required state
Key: WFLY-8254
URL: https://issues.jboss.org/browse/WFLY-8254
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Martin Choma
Assignee: Darran Lofthouse
Attribute sasl-authentication-factory is described as follows
{code}
"sasl-authentication-factory" => {
"type" => STRING,
"description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"capability-reference" => "org.wildfly.security.sasl-authentication-factory",
"min-length" => 1L,
"max-length" => 2147483647L
}
{code}
Documenation [1] says:
no-services – Applying the operation to the runtime does not require the restart of any services. This value is the default if the restart-required descriptor is not present.
But when I try to change it I get:
{code}
[standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=application-sasl-authentication)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{code}
Probably some proper value for "restart-required" should be used. "restart-required" => "all-services" ?
[1] https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month