June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1600) Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1600?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1600: ------------------------------------- Fix Version/s: 3.0.0.Alpha3 (was: 3.0.0.Alpha2) > Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances. > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1600 > URL: https://issues.jboss.org/browse/WFCORE-1600 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha3 > > > These are for use when security realms are directly referenced, although Elytron types these should not be advertised as capabilities as these are for specific backwards compatibility requirements and not to increase their use as Elytron capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6745) Support for SSL out of the box

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6745?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved WFCORE-1605 to WFLY-6745: ---------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-6745 (was: WFCORE-1605) Fix Version/s: 10.1.0.Final (was: 2.2.0.CR3) (was: 3.0.0.Alpha2) > Support for SSL out of the box > ------------------------------ > > Key: WFLY-6745 > URL: https://issues.jboss.org/browse/WFLY-6745 > Project: WildFly > Issue Type: Feature Request > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1605) Support for SSL out of the box

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-1605: -------------------------------------- Summary: Support for SSL out of the box Key: WFCORE-1605 URL: https://issues.jboss.org/browse/WFCORE-1605 Project: WildFly Core Issue Type: Feature Request Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 2.2.0.CR3, 3.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1418) Reloading host-controller via http-api puts the HC into unresponsive state

by ebuzer taha kanat (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1418?page=com.atlassian.jira.plugi... ] ebuzer taha kanat commented on WFCORE-1418: ------------------------------------------- suspending server before reload solves the undertow closing problem but still some times reload problem exist i think i diagnosed problem wrong. > Reloading host-controller via http-api puts the HC into unresponsive state > -------------------------------------------------------------------------- > > Key: WFCORE-1418 > URL: https://issues.jboss.org/browse/WFCORE-1418 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.10.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 2.1.0.Final > > > Reloading host-controller via http-api puts the HC into unresponsive state. > *reproduce* > \- create an administrative user admin:asdasd@2 > \- start a domain > \- reload a server via http api > {noformat} > curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"operation":"reload","name":"", "address":{"host" : "master"},"json.pretty":1}' -u admin:asdasd@2 > {noformat} > *actual* > Default server instances are stopped, HC is left in unresponsive state. > Keeping the domain alive, following message will appear in 5 minutes, domain will become responsive again after that. > {noformat} > [Host Controller] 04:47:23,966 ERROR [org.jboss.as.controller.management-operation] (management task-7) WFLYCTL0349: Timeout after [300] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'reload' at address '[("host" => "master")]' > {noformat} > *expected* > Domain is reloaded > *additional info* > The issue was introduced by fix for JBEAP-2751 - https://github.com/jbossas/wildfly-core-eap/commit/4986773a51fbf43ad911ae... > thread dump of unresponsive HC > http://pastebin.test.redhat.com/348732 > I am unable to reproduce locally, but issue can be easily reproduced on slower servers in MWQE lab. SSLMasterSlave*WayTestCase using reload via http-api cousing failures in domain modules of wf-core testsuite (e.g. [eap-7x-as-testsuite-test-core-rhel|https://url.corp.redhat.com/9f1f544] ) > Regression against 7.0.0.ER4. I was able to reproduce with the latest wildfly-core bits as well (1be598e) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1228) Follow up on WFCORE-1202 and make the configuration available in the management model.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1228?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1228: ------------------------------------- Fix Version/s: 2.2.0.CR4 (was: 2.2.0.CR3) > Follow up on WFCORE-1202 and make the configuration available in the management model. > -------------------------------------------------------------------------------------- > > Key: WFCORE-1228 > URL: https://issues.jboss.org/browse/WFCORE-1228 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 2.2.0.CR4 > > > WFCORE-1202 makes use of a system property for configuration, this needs moving into the management model. > The system property should remain supported for backwards compatibility for those migrating from servers that relied on it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6663) NPE o.j.a.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238)

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-6663?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-6663: ------------------------------------ >> Is https://issues.jboss.org/browse/WFLY-6638 related? The fix for that has been merged upstream, so you can try the nightly build (https://developer.jboss.org/thread/224262) and see if it fixes your issue. > NPE o.j.a.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238) > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-6663 > URL: https://issues.jboss.org/browse/WFLY-6663 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Environment: Win7 64bit + JDK8 64bit > Reporter: Darryl Miles > > 1 in 8 deployments fail to deploy, usually a redeploy fixes it. > If there is anyway to get a module state logging out of it, I can send over two logs to compare, one that deploy ok and one that fails. I guess there is a race bug there somewhere. > 09:42:01,687 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 529) MSC000001: Failed to start service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."com.domain.ear-0.0.1-SNAPSHOT.ear"."com-domain-ejb.main-0.0.1-SNAPSHOT.jar".component.MainStartupEjbImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) > at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:124) > at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:138) > at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) > ... 6 more > Caused by: javax.ejb.EJBException: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb > at org.jboss.as.ejb3.tx.BMTInterceptor.handleException(BMTInterceptor.java:83) > at org.jboss.as.ejb3.tx.EjbBMTInterceptor.checkStatelessDone(EjbBMTInterceptor.java:91) > 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:340) > at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) > ... 11 more > Caused by: java.lang.RuntimeException: WFLYNAM0059: Resource lookup for injection failed: env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb > at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:319) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:97) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:107) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103) > ... 26 more > Caused by: javax.naming.NamingException: WFLYNAM0062: Failed to lookup env/com.domain.ejb.main.impl.MainStartupEjbImpl/mainEjb [Root exception is java.lang.RuntimeException: WFLYEJB0423: Could not create session for stateful bean MainEjbImpl] > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:157) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at org.jboss.as.naming.deployment.ContextNames$BindInfo$1$1.getReference(ContextNames.java:316) > ... 43 more > Caused by: java.lang.RuntimeException: WFLYEJB0423: Could not create session for stateful bean MainEjbImpl > at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:99) > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:143) > ... 48 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238) > at org.jboss.as.ejb3.remote.LocalEjbReceiver.openSession(LocalEjbReceiver.java:296) > at org.jboss.ejb.client.EJBClient.createSessionWithPossibleRetries(EJBClient.java:225) > at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:202) > at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:176) > at org.jboss.as.ejb3.remote.RemoteViewManagedReferenceFactory.getReference(RemoteViewManagedReferenceFactory.java:97) > ... 49 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1381) wildfly-init-debian.sh fails on Ubuntu 15.04

by Jorge Solorzano (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1381?page=com.atlassian.jira.plugi... ] Jorge Solorzano commented on WFCORE-1381: ----------------------------------------- It should be noted that the correct way to use it is to copy the init.d and conf files to their respective directories because a symbolic link would create a security exploit should anyone be able to gain the permissions of wildfly and modify $JBOSS_HOME/bin/init.d/wildfly-init-debian.sh. Please don't make a symbolic link to this files. I'm going to create a README with the steps to install as a service. > wildfly-init-debian.sh fails on Ubuntu 15.04 > -------------------------------------------- > > Key: WFCORE-1381 > URL: https://issues.jboss.org/browse/WFCORE-1381 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 1.0.0.Beta6, 1.0.0.CR1 > Environment: Ubuntu 15.04, Oracle JDK_1.8.0_45-b14 > Reporter: Dennis Gesker > Priority: Minor > > Init script "wildfly-init-debian.sh" fails on Ubuntu 15.04 but standalone.sh works fine. Env is jdk_1.8.0_45-b14 and wildfly_9.0.0.Beta2. The error returned is: > Failed to start wildfly.service: Unit wildfly.service failed to load: No such file or directory. > Had no issue with the above script on Ubuntu 14.04 so guessing a change in Ubuntu ("Upstart" Maybe?) But, I'm far from an upstart or bash expert. bash -x seems to at least create the pid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-545) Missing null checks in URIUtil.getHostForURI(SocketAddress socketAddress) method

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-545?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-545. ----------------------------- Fix Version/s: 1.1.0.Beta7 Resolution: Done > Missing null checks in URIUtil.getHostForURI(SocketAddress socketAddress) method > -------------------------------------------------------------------------------- > > Key: ELY-545 > URL: https://issues.jboss.org/browse/ELY-545 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta5 > Reporter: Ondrej Lukas > Assignee: David Lloyd > Labels: static_analysis > Fix For: 1.1.0.Beta7 > > > There is public static method org.wildfly.security.util.URIUtil.getHostForURI(SocketAddress socketAddress) with missing null checks for {{hostString}} and {{address}}. This method can be publicly accessed and result to NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-546) Missing null check in SecurityDomain.mapName() method

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-546?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-546. ----------------------------- Fix Version/s: 1.1.0.Beta7 Resolution: Done > Missing null check in SecurityDomain.mapName() method > ----------------------------------------------------- > > Key: ELY-546 > URL: https://issues.jboss.org/browse/ELY-546 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta5 > Reporter: Ondrej Lukas > Assignee: David Lloyd > Labels: static_analysis > Fix For: 1.1.0.Beta7 > > > There is missing null check in org.wildfly.security.auth.server.SecurityDomain.mapName(String name) method. Parameter {{name}} can be changed to null on line 162 [1] which can result to NPE in following command on line 163. Null check should be added. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/ef67225884aa79b8... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-542) Incorrectly implemented applyFilter method of ProtocolSelector.RemovingProtocolSelector

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-542?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-542. ----------------------------- Fix Version/s: 1.1.0.Beta7 Resolution: Done > Incorrectly implemented applyFilter method of ProtocolSelector.RemovingProtocolSelector > --------------------------------------------------------------------------------------- > > Key: ELY-542 > URL: https://issues.jboss.org/browse/ELY-542 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta5 > Reporter: Ondrej Lukas > Assignee: David Lloyd > Labels: static_analysis > Fix For: 1.1.0.Beta7 > > > Method applyFilter from org.wildfly.security.ssl.ProtocolSelector.RemovingProtocolSelector is incorrectly implemented. {{Set<Protocol> enabled}} cannot contain (and therefore cannot remove) {{EnumSet<Protocol> protocols}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2016