March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8479) add jaxrs integration tests to check registration of resources in mgt model

by R Searls (JIRA)

R Searls created WFLY-8479: ------------------------------ Summary: add jaxrs integration tests to check registration of resources in mgt model Key: WFLY-8479 URL: https://issues.jboss.org/browse/WFLY-8479 Project: WildFly Issue Type: Task Components: REST Affects Versions: 11.0.0.Beta1 Reporter: R Searls Assignee: R Searls Priority: Trivial WFLY-8026 was about proper registration of jaxrs app resources in the mgt model. It is desirable to added integration tests to confirm registration is working with the various ways a REST app can be defined. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1471) Unable to marshall a kieSession running in stream mode.

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1471?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1471. --------------------------------- Resolution: Rejected Serialization requires a snapshot of the session, so it can't be done while a fireUntilHalt is concurrently running. > Unable to marshall a kieSession running in stream mode. > ------------------------------------------------------- > > Key: DROOLS-1471 > URL: https://issues.jboss.org/browse/DROOLS-1471 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final, 6.5.0.Final > Reporter: Manjunath S Paramesan > Assignee: Mario Fusco > > Runtime exceptions are thrown when Marshalling a KieSession in runtime. Please see the stack trace below: > java.util.concurrent.ExecutionException: java.lang.NullPointerException > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at drools.tester.drools.marshallng.tester.ReproducerTest.test(ReproducerTest.java:91) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > Caused by: java.lang.NullPointerException > at org.drools.core.util.index.TupleList.removeFirst(TupleList.java:142) > at org.drools.core.phreak.RuleExecutor.getNextTuple(RuleExecutor.java:167) > at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:107) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350) > at org.drools.core.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:1269) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1345) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1324) > at drools.tester.drools.marshallng.tester.ReproducerTest$1.run(ReproducerTest.java:73) > 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) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2603) Upgrade WildFly Elytron Tool to 1.0.0.Beta1

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2603: ---------------------------------------- Summary: Upgrade WildFly Elytron Tool to 1.0.0.Beta1 Key: WFCORE-2603 URL: https://issues.jboss.org/browse/WFCORE-2603 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta12 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2602) Upgrade WildFly Elytron to 1.1.0.Beta34

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2602: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.1.0.Beta34 Key: WFCORE-2602 URL: https://issues.jboss.org/browse/WFCORE-2602 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Beta12 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1045) Release WildFly Elytron 1.1.0.Beta34

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1045: ------------------------------------- Summary: Release WildFly Elytron 1.1.0.Beta34 Key: ELY-1045 URL: https://issues.jboss.org/browse/ELY-1045 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta34 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1032) Help output has limit for line length 160 chars and it leads to ugly line break in the middle of one option.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1032?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1032: ------------------------------------- Assignee: Peter Skopek (was: Darran Lofthouse) > Help output has limit for line length 160 chars and it leads to ugly line break in the middle of one option. > ------------------------------------------------------------------------------------------------------------ > > Key: ELY-1032 > URL: https://issues.jboss.org/browse/ELY-1032 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Hynek Švábek > Assignee: Peter Skopek > Fix For: 1.1.0.Beta34 > > > Help output has limit 160 chars for line length and it leads to ugly line break in the middle of one option. > Command > {code} > java -jar wildfly-elytron-tool.jar credential-store --help > {code} > has this output: > {code} > usage: java -jar wildfly-elytron-tool.jar credential-store -a <alias> | -e <alias> | -h | -r <alias> | -v [-c] [-f] [-i <arg>] [-l <loc>] [-p <pwd>] [-s > <arg>] [-t <type>] [-u <uri>] [-x <secret to store>] > {code} > I expect at least line break before "-s" option > {code} > usage: java -jar wildfly-elytron-tool.jar credential-store -a <alias> | -e <alias> | -h | -r <alias> | -v [-c] [-f] [-i <arg>] [-l <loc>] [-p <pwd>] > [-s <arg>] [-t <type>] [-u <uri>] [-x <secret to store>] > {code} > The best option would be some dynamic settings of line length -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1032) Help output has limit for line length 160 chars and it leads to ugly line break in the middle of one option.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1032?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1032: ---------------------------------- Fix Version/s: 1.1.0.Beta34 > Help output has limit for line length 160 chars and it leads to ugly line break in the middle of one option. > ------------------------------------------------------------------------------------------------------------ > > Key: ELY-1032 > URL: https://issues.jboss.org/browse/ELY-1032 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Hynek Švábek > Assignee: Peter Skopek > Fix For: 1.1.0.Beta34 > > > Help output has limit 160 chars for line length and it leads to ugly line break in the middle of one option. > Command > {code} > java -jar wildfly-elytron-tool.jar credential-store --help > {code} > has this output: > {code} > usage: java -jar wildfly-elytron-tool.jar credential-store -a <alias> | -e <alias> | -h | -r <alias> | -v [-c] [-f] [-i <arg>] [-l <loc>] [-p <pwd>] [-s > <arg>] [-t <type>] [-u <uri>] [-x <secret to store>] > {code} > I expect at least line break before "-s" option > {code} > usage: java -jar wildfly-elytron-tool.jar credential-store -a <alias> | -e <alias> | -h | -r <alias> | -v [-c] [-f] [-i <arg>] [-l <loc>] [-p <pwd>] > [-s <arg>] [-t <type>] [-u <uri>] [-x <secret to store>] > {code} > The best option would be some dynamic settings of line length -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1014) Elytron auth method misconfiguration not logged

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1014?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1014: ---------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/746 (was: https://github.com/wildfly-security/wildfly-elytron/pull/732) > Elytron auth method misconfiguration not logged > ----------------------------------------------- > > Key: ELY-1014 > URL: https://issues.jboss.org/browse/ELY-1014 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Blocker > Labels: user_experience > > When deployment is configured to be secured with DIGEST, but {{http-authentication-factory}} does not list DIGEST mechanism, user is not informed about misconfiguration. Even when TRACE logging is turned on. When user tries to access app 403 http code is returned and Forbidden is shown in browser. I would expect browser dialog to appear to allow user provide credentials (401 http status code). > {code:title=web.xml} > <login-config> > <auth-method>DIGEST</auth-method> > <realm-name>ApplicaitonRealm</realm-name> > </login-config> > {code} > {code:title=standalone-elytron.xml} > <http-authentication-factory name="application-http-authentication" http-server-mechanism-factory="global" security-domain="ApplicationDomain"> > <mechanism-configuration> > <mechanism mechanism-name="BASIC"> > <mechanism-realm realm-name="Application Realm"/> > </mechanism> > <mechanism mechanism-name="FORM"/> > </mechanism-configuration> > </http-authentication-factory> > {code} > This applies globally to all authentication mechanisms, not only DIGEST. > Could elytron handle misconfiguration: > * either fail during deploying application as deployment requirement can't be satisfy > * or provide reasonable elytron defaults of missing mechanism configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8478) Setting elytron ssl-context on undertow without reload

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8478?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8478: ---------------------------------------- This is true, but we should be careful about simple advice to use {allow-resource-service-restart=true}. That's a power user setting that should only be used by people with a very clear understanding of the effects. It's not in any way a "better reload". In this case {allow-resource-service-restart=true} is likely more useful, since I don't *think* bouncing the listener service will have widely cascading effects. But any advice to use {allow-resource-service-restart=true} should always include some comment on what the expected effects would be. The end user will very likely not have a clue and an uneducated guess will likely be too optimistic by far. BTW, I'm not arguing with rejecting this issue if there is no reasonable way to update the service without a service restart. And I have reason to believe there is such a way. My point is just about what message we send to end users. > Setting elytron ssl-context on undertow without reload > ------------------------------------------------------ > > Key: WFLY-8478 > URL: https://issues.jboss.org/browse/WFLY-8478 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Reporter: Martin Choma > Assignee: Tomaz Cerar > Labels: user_experience > > Please, allow setting of elytron ssl-context on undertow without reload. > {code} > [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/https-listener=https:write-attribute(name=ssl-context,value=server) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-82) JMAN4 Feature Requests Test Cases Review

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-82: ---------------------------------------- Summary: JMAN4 Feature Requests Test Cases Review Key: HAWKULARQE-82 URL: https://issues.jboss.org/browse/HAWKULARQE-82 Project: Hawkular QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Priority: Critical Go through all JMAN4 Features and their QE tasks: Make sure that all existing Polarion testcases are created and mentioned in QE tasks. Review polarion testcases, make comments on QE tasks to fix testcases if necessary. If testcases are missing, request to create them. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2017