March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9707) Remove JASPI module

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9707?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9707: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Remove JASPI module > ------------------- > > Key: WFLY-9707 > URL: https://issues.jboss.org/browse/WFLY-9707 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9702) SSO Integration for Programmatic Authentication

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9702?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9702: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > SSO Integration for Programmatic Authentication > ----------------------------------------------- > > Key: WFLY-9702 > URL: https://issues.jboss.org/browse/WFLY-9702 > Project: WildFly > Issue Type: Bug > Components: Clustering, Security, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 13.0.0.Beta1 > > > At the moment the SSO integration only fully covers authentication mechanisms as they can be wrapped, we need to revisit for programmatic authentication. > In this scenario we don't have either a wrapped mechanism or a CallbackHandler. > Couple of options: - > * Can we get away with pushing in some form of IdentityCache factory the mechs can obtain from the request? This may miss the additional notifications the SSO impl depends on. > * Can we also better support listening for the notifications without the need for wrappers? This could cover both mechs and programmatic authentication? > * Instead do we make the programmatic authenticator pluggable, i.e. push in an SSO aware impl, it can choose how to handle it's own caching and also doesn't need the notifications as it is in control of that stage of the process. > * -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9903) Cannot remove modcluster subsystem for the first time

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9903?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9903: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Cannot remove modcluster subsystem for the first time > ----------------------------------------------------- > > Key: WFLY-9903 > URL: https://issues.jboss.org/browse/WFLY-9903 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 12.0.0.Beta1 > Environment: Debian stable, openjdk 8 > Reporter: Marcel Šebek > Assignee: Radoslav Husar > Priority: Critical > Fix For: 13.0.0.Beta1 > > > Removal of modcluster subsystem first produces an error, and succeeds for the second time: > [standalone@localhost:9990 /] /subsystem=modcluster:remove() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0441: Operation has resulted in failed or missing services > WFLYCTL0184: New missing/unsatisfied dependencies: > service org.wildfly.mod_cluster.undertow (unavailable) dependents: [service org.wildfly.undertow.http-invoker.host.default-host.http-invoker] > ", > "rolled-back" => true > } > [standalone@localhost:9990 /] /subsystem=modcluster:remove() > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > Error in the wildfly output is > 18:35:11,316 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 78) MODCLUSTER000002: Initiating mod_cluster shutdown > 18:35:11,319 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("remove") failed - address: ([("subsystem" => "modcluster")]) - failure description: "WFLYCTL0441: Operation has resulted in failed or missing services > WFLYCTL0184: New missing/unsatisfied dependencies: > service org.wildfly.mod_cluster.undertow (unavailable) dependents: [service org.wildfly.undertow.http-invoker.host.default-host.http-invoker] > " > 18:35:11,321 INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service org.wildfly.mod_cluster.undertow (unavailable) dependents: [service org.wildfly.undertow.http-invoker.host.default-host.http-invoker] > For the second time, it succeeds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9801) Wsprovide tool ends with java.security.AccessControlException

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9801?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9801: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Wsprovide tool ends with java.security.AccessControlException > ------------------------------------------------------------- > > Key: WFLY-9801 > URL: https://issues.jboss.org/browse/WFLY-9801 > Project: WildFly > Issue Type: Bug > Components: Scripts, Web Services > Reporter: Marek Kopecký > Assignee: R Searls > Priority: Critical > Fix For: 13.0.0.Beta1 > > Attachments: Echo1-security.policy, Echo1.class, Echo1Impl.class > > > *Description of the issue:* > wsprovide tool ends with java.security.AccessControlException > I see this issue on WF master (2018_02_12). This is regression against WF master from 2018_02_05, so priority of this jira is blocker. > *How reproducible:* > Always > *Steps to Reproduce:* > # Use these (class files are attached): > {code:java} > @WebService(endpointInterface = "org.jboss.as.testsuite.integration.scripts.test.tools.Echo1", targetNamespace = "org.jboss.as.testsuite.integration.scripts.test.tools", serviceName = "Echo1Service") > public class Echo1Impl implements Echo1 { > @Override > public String echoPlus1(String s) { > return s + "1"; > } > } > {code} > {code:java} > @WebService > @SOAPBinding > public interface Echo1 { > String echoPlus1(String s); > } > {code} > # cd $\{JBOSS_HOME\}/bin > # mkdir out > # ./wsprovide.sh -k -c $\{CLASS_DIR\} -o out org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl > *Actual results:* > {noformat} > [mkopecky@localhost bin]$ ./wsprovide.sh -k -c ~/erase2 -o out org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl > Could not find log4j.properties or log4j.xml configuration, logging to console. > java2ws -s /home/mkopecky/playground/wf/wfly.13/wfly.13/bin/out -classdir /home/mkopecky/playground/wf/wfly.13/wfly.13/bin/out -d /home/mkopecky/playground/wf/wfly.13/wfly.13/bin/out -verbose -cp /home/mkopecky/erase2/: -wrapperbean -createxsdimports org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl > java2ws - Apache CXF 3.2.2 > java.security.AccessControlException: access denied ("java.io.FilePermission" "/home/mkopecky/playground/wf/wfly.13/wfly.13/bin/out/org/jboss/as/testsuite/integration/scripts/test/tools/jaxws/EchoPlus1Response.java" "read") > at java.security.AccessControlContext.checkPermission(AccessControlContext.java:472) > at java.security.AccessController.checkPermission(AccessController.java:884) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:549) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at java.io.File.isDirectory(File.java:844) > at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:69) > at com.sun.tools.javac.file.RegularFileObject.<init>(RegularFileObject.java:64) > at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromFiles(JavacFileManager.java:785) > at com.sun.tools.javac.file.JavacFileManager.getJavaFileObjectsFromStrings(JavacFileManager.java:185) > at org.apache.cxf.common.util.Compiler.useJava6Compiler(Compiler.java:202) > at org.apache.cxf.common.util.Compiler.compileFiles(Compiler.java:141) > at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.generateAndCompile(BeanGenerator.java:91) > at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.generate(BeanGenerator.java:58) > at org.apache.cxf.tools.java2wsdl.generator.wsdl11.BeanGenerator.generate(BeanGenerator.java:35) > at org.apache.cxf.tools.java2wsdl.processor.JavaToWSDLProcessor.generate(JavaToWSDLProcessor.java:156) > at org.apache.cxf.tools.java2wsdl.processor.JavaToWSDLProcessor.process(JavaToWSDLProcessor.java:118) > at org.apache.cxf.tools.java2ws.JavaToWSContainer.processWSDL(JavaToWSContainer.java:110) > at org.apache.cxf.tools.java2ws.JavaToWSContainer.execute(JavaToWSContainer.java:75) > at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105) > at org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:45) > at org.apache.cxf.tools.java2ws.JavaToWS.run(JavaToWS.java:83) > at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(CXFProviderImpl.java:200) > at org.jboss.wsf.stack.cxf.tools.CXFProviderImpl.provide(CXFProviderImpl.java:109) > at org.jboss.ws.tools.cmd.WSProvide.generate(WSProvide.java:223) > at org.jboss.ws.tools.cmd.WSProvide.main(WSProvide.java:89) > at org.jboss.modules.Module.runMainMethod(Module.java:348) > at org.jboss.modules.Module.run(Module.java:328) > at org.jboss.modules.Main.main(Main.java:557) > {noformat} > *Expected results:* > No errors -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9791) Add Elytron Web undertow-servlet module

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9791?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9791: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Add Elytron Web undertow-servlet module > --------------------------------------- > > Key: WFLY-9791 > URL: https://issues.jboss.org/browse/WFLY-9791 > Project: WildFly > Issue Type: Sub-task > Components: Build System, Security, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9854) jgroups-channel cannot use name which is already used by jgroups/stacks

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFLY-9854?page=com.atlassian.jira.plugin.... ] Erich Duda commented on WFLY-9854: ---------------------------------- Thanks all for your inputs. [~ccopello] The EAP7-941 looks like documentation Jira for RFE, but this is only bug. Can you double check it? Thank you. > jgroups-channel cannot use name which is already used by jgroups/stacks > ----------------------------------------------------------------------- > > Key: WFLY-9854 > URL: https://issues.jboss.org/browse/WFLY-9854 > Project: WildFly > Issue Type: Bug > Components: Clustering, JMS > Affects Versions: 12.0.0.Beta1 > Reporter: Erich Duda > Assignee: Paul Ferraro > Priority: Blocker > > The configuration \[1\] results to an error \[2\]. This is backward compatibility issue since the configuration works with previous releases of Wildfly. > \[1\] > {code:xml} > <broadcast-group name="bg-group1" jgroups-stack="udp" jgroups-channel="udp" broadcast-period="2000" connectors="connector"/> > {code} > \[2\] > {code} > 10:52:29,982 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 15) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "jgroups"), > ("channel" => "udp") > ]) - failure description: "WFLYCTL0436: Cannot register capability 'org.wildfly.clustering.jgroups.channel-factory.udp' at location '[ > (\"subsystem\" => \"jgroups\"), > (\"channel\" => \"udp\") > ]' as it is already registered in context 'global' at location(s) '[[ > (\"subsystem\" => \"jgroups\"), > (\"stack\" => \"udp\") > ]]'" > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6777) Upgrade to OpenJPA impl compatible with JDK9

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-6777?page=com.atlassian.jira.plugin.... ] Jason Greene resolved WFLY-6777. -------------------------------- Resolution: Done > Upgrade to OpenJPA impl compatible with JDK9 > -------------------------------------------- > > Key: WFLY-6777 > URL: https://issues.jboss.org/browse/WFLY-6777 > Project: WildFly > Issue Type: Sub-task > Components: JPA / Hibernate > Reporter: Tomaz Cerar > Assignee: Scott Marlow > Priority: Minor > Fix For: 12.0.0.Beta1, 12.0.0.Final > > > OpenJPA tests currently hang our testsuite as serp bytecode enhancer that OpenJPA uses hangs the deployment. > For now test is not run on JDK9, but this should be re-enabled once there is release of openjpa that works fine with jdk9 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9413) Update EclipseLink module to remove unused asm/javassist dependencies

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9413?page=com.atlassian.jira.plugin.... ] Jason Greene resolved WFLY-9413. -------------------------------- Resolution: Done > Update EclipseLink module to remove unused asm/javassist dependencies > --------------------------------------------------------------------- > > Key: WFLY-9413 > URL: https://issues.jboss.org/browse/WFLY-9413 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.Beta1, 12.0.0.Final > > > The EclipseLink module doesn't depend on asm/javassist modules. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9841) upgrade org.jboss.spec.javax.enterprise.concurrent:jboss-concurrency-api_1.0_spec to 1.0.2.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9841?page=com.atlassian.jira.plugin.... ] Jason Greene resolved WFLY-9841. -------------------------------- Resolution: Done > upgrade org.jboss.spec.javax.enterprise.concurrent:jboss-concurrency-api_1.0_spec to 1.0.2.Final > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9841 > URL: https://issues.jboss.org/browse/WFLY-9841 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.CR1, 12.0.0.Final > > > Updated license file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9866) (EE8 mode of) module javax.faces.api needs a dependency on javax.websocket.api

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9866?page=com.atlassian.jira.plugin.... ] Jason Greene resolved WFLY-9866. -------------------------------- Resolution: Done > (EE8 mode of) module javax.faces.api needs a dependency on javax.websocket.api > ------------------------------------------------------------------------------ > > Key: WFLY-9866 > URL: https://issues.jboss.org/browse/WFLY-9866 > Project: WildFly > Issue Type: Task > Components: JSF > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.CR1, 12.0.0.Final > > > Noticed during EE 8 testing, that javax.faces.event.WebsocketEvent needs a dependency on javax.websocket.CloseReason, so we probably need something like: > {code} > <module name="javax.faces.api" xmlns="urn:jboss:module:1.7"> > <dependencies> > <module name="com.sun.jsf-impl"/> > <module name="javax.enterprise.api" export="true"/> > <module name="javax.servlet.api" export="true"/> > <module name="javax.servlet.jsp.api" export="true"/> > <module name="javax.servlet.jstl.api" export="true"/> > <module name="javax.validation.api" export="true"/> > <module name="org.glassfish.javax.el" export="true"/> > <module name="javax.api"/> > <module name="javax.websocket.api"/> > </dependencies> > <resources> > <resource-root path="jboss-jsf-api_2.2_spec-2.2.14.jar"> > <conditions> > <property-not-equal name="ee8.preview.mode" value="true"/> > </conditions> > </resource-root> > <resource-root path="jboss-jsf-api_2.3_spec-2.3.3.SP1.jar"> > <conditions> > <property-equal name="ee8.preview.mode" value="true"/> > </conditions> > </resource-root> > </resources> > </module> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 March 2018