March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6396) Elytron integration with the mail subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6396?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6396: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Elytron integration with the mail subsystem > ------------------------------------------- > > Key: WFLY-6396 > URL: https://issues.jboss.org/browse/WFLY-6396 > Project: WildFly > Issue Type: Feature Request > Components: Mail > Reporter: Darran Lofthouse > Assignee: Peter Skopek > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6732) IllegalStateException in ApplicationSecurityDomainService#initialSecurityHandler when loginConfig is null

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6732?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6732: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > IllegalStateException in ApplicationSecurityDomainService#initialSecurityHandler when loginConfig is null > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-6732 > URL: https://issues.jboss.org/browse/WFLY-6732 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > Fix For: 11.0.0.Beta1 > > > The following IllegalStateException occurs when attempting to deploy an application that doesn't specify the {{login-config}}: > {code} > java.lang.IllegalStateException: WFLYUT0084: No authentication mechanisms have been selected. > at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.initialSecurityHandler(ApplicationSecurityDomainDefinition.java:345) > at org.wildfly.extension.undertow.ApplicationSecurityDomainDefinition$ApplicationSecurityDomainService.lambda$applyElytronSecurity$0(ApplicationSecurityDomainDefinition.java:295) > at io.undertow.servlet.core.DeploymentManagerImpl.setupSecurityHandlers(DeploymentManagerImpl.java:400) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:204) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7161) EJB with defined specific security domain which is different than the one used for undertow fails when using with elytron

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7161?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7161: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > EJB with defined specific security domain which is different than the one used for undertow fails when using with elytron > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7161 > URL: https://issues.jboss.org/browse/WFLY-7161 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Radim Hatlapatka > Assignee: Darran Lofthouse > Fix For: 11.0.0.Beta1 > > > When having deployment with EJB which is invoked from servlet and the EJB has defined specific security domain to use via {{@SecurityDomain}} annotation, the ejb method invocation fails when there is defined elytron security domain for undertow and old security domain for EJBs with \[1\]. > Note when having both security domains setup only using old security subsystems, the access is allowed as expected. > Marking as critical as this should work. If it is not considered supported use case then there should be at least shown proper warning in logs explaining what is wrong. > \[1\] > {noformat} > 09:30:03,749 ERROR [org.jboss.as.ejb3.invocation] (default task-25) WFLYEJB0034: EJB Invocation failed on component SecuredEjb for method public java.lang.String org.jboss.qa.management.web.resources.SecuredEjb.securedText(): javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public java.lang.String org.jboss.qa.management.web.resources.SecuredEjb.securedText() of bean: SecuredEjb is not allowed > at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:134) > 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.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 org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > 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.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:74) > at org.jboss.qa.management.web.resources.SecuredEjb$$$view6.securedText(Unknown Source) > at org.jboss.qa.management.web.resources.ServletWithSecuredEjb.doGet(ServletWithSecuredEjb.java:27) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.elytron.web.undertow.server.ElytronRunAsHandler.lambda$handleRequest$0(ElytronRunAsHandler.java:56) > at org.wildfly.security.auth.client.PeerIdentity.runAsAll(PeerIdentity.java:395) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:188) > at org.wildfly.elytron.web.undertow.server.ElytronRunAsHandler.handleRequest(ElytronRunAsHandler.java:55) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1668) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:810) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7116) High CPU usage during high concurrency of distributed @Stateful EJB creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7116?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7116: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > High CPU usage during high concurrency of distributed @Stateful EJB creation > ---------------------------------------------------------------------------- > > Key: WFLY-7116 > URL: https://issues.jboss.org/browse/WFLY-7116 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7119) Introduce new web session granularity for consistent fine granularity replication

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7119?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7119: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Introduce new web session granularity for consistent fine granularity replication > --------------------------------------------------------------------------------- > > Key: WFLY-7119 > URL: https://issues.jboss.org/browse/WFLY-7119 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > Currently, ATTRIBUTE granularity sessions are vulnerable to partial stale reads, where some session attributes might have current data, and some are stale. For some use cases, this might be intolerable. For these use cases, we should introduce a new session granularity that tracks a version or checksum per attribute, that we can use to detect stale attribute cache entries. > This new granularity would retain the performance benefits of ATTRIBUTE granularity replication while maintaining the attribute consistency guarantees of SESSION granularity replication. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6973) Upgrade Infinispan to 9.0

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6973?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-6973: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Upgrade Infinispan to 9.0 > ------------------------- > > Key: WFLY-6973 > URL: https://issues.jboss.org/browse/WFLY-6973 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7100) Add JGroups-based SingletonServiceBuilderFactory implementation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7100?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7100: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Add JGroups-based SingletonServiceBuilderFactory implementation > --------------------------------------------------------------- > > Key: WFLY-7100 > URL: https://issues.jboss.org/browse/WFLY-7100 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > The singleton subsystem currently requires the Infinispan subsystem. To minimize the requirements for using the singleton subsystem within the context of the host-controller, we should reimplement singleton service using JGroups directly, instead of requiring an Infinispan cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7117) High CPU usage during high concurrency of distributed SSO creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7117?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7117: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > High CPU usage during high concurrency of distributed SSO creation > ------------------------------------------------------------------ > > Key: WFLY-7117 > URL: https://issues.jboss.org/browse/WFLY-7117 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7115) High CPU usage during high concurrency of distributed web session creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7115?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7115: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > High CPU usage during high concurrency of distributed web session creation > -------------------------------------------------------------------------- > > Key: WFLY-7115 > URL: https://issues.jboss.org/browse/WFLY-7115 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > Replace usage of KeyAffinityService with AffinityTaggedKey. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7041) Add testing for Web -> EJB Identity Propagation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7041?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7041: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Add testing for Web -> EJB Identity Propagation > ----------------------------------------------- > > Key: WFLY-7041 > URL: https://issues.jboss.org/browse/WFLY-7041 > Project: WildFly > Issue Type: Task > Components: EJB, Security, Test Suite > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Labels: elytron_testing > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017