March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2606) Wildfly OpenSSL 1.0.0.CR1

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2606?page=com.atlassian.jira.plugi... ] Stuart Douglas moved JBEAP-10042 to WFCORE-2606: ------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2606 (was: JBEAP-10042) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Wildfly OpenSSL 1.0.0.CR1 > ------------------------- > > Key: WFCORE-2606 > URL: https://issues.jboss.org/browse/WFCORE-2606 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3860) Improve dependency handling in clustering/infinispan subsystem tests

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3860?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned WFLY-3860: ------------------------------------ Assignee: Radoslav Husar > Improve dependency handling in clustering/infinispan subsystem tests > -------------------------------------------------------------------- > > Key: WFLY-3860 > URL: https://issues.jboss.org/browse/WFLY-3860 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 9.0.0.Alpha1 > Reporter: Brian Stansberry > Assignee: Radoslav Husar > > The subsystem tests in clustering/infinispan are not configured to use a controller operating in --admin-only mode, but they are also not doing all the needed setup to have needed services and resources (core, jmx, jgroups) available for when the services they add are started. > This is fragile, because all sorts of stuff is failing when things are getting launched, but the tests are not noticing that. That's ok right now, but it could lead to missing regressions. > Also, the changes I'm making for WFCORE-102 mean these problems will no longer go unnoticed and the tests will fail. > I plan to: > 1) Shifts tests to using --admin-only in cases where the tests are clearly not testing anything related to runtime execution; i.e. they are just testing model. > 2) For OperationSequencesTestCase and OperationsTestCase, where there is some validation of runtime behavior going on (explicit in some places; in others perhaps expected, perhaps not) I'm going to switch the tests to a more focused config file that: > a) Only uses local caches, to avoid pulling in requirements for jgroups things that are not present. (I see no indication any of the tests are testing anything not present with local caches.) > b) Uses start="LAZY". This means services will get registered, but not started. Not starting avoids detection of various missing dependencies, including a ModuleLoader dependency that I can't figure out how to satisfy. > The tests can't be trying to validate any behavior when services start, because they've never been able to start. So LAZY is fine. Some tests do seem to be looking for problem related to service conflicts as resources are added/removed. These tests are still valid, because service conflicts happen as soon as services are installed, whether or not the services need to start. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2181) Server doesn't start on Windows when started from path that contains space

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2181?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-2181. -------------------------------------- Fix Version/s: 3.0.0.Beta12 (was: 3.0.0.Alpha18) Resolution: Done > Server doesn't start on Windows when started from path that contains space > -------------------------------------------------------------------------- > > Key: WFCORE-2181 > URL: https://issues.jboss.org/browse/WFCORE-2181 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 3.0.0.Beta12 > > > If one installs his EAP(on Windows) to the location that has a space in the path(...\Program Files\...) is then unable to start it. > This is regression against EAP 7.0.0 and 7.1.0.DR7. > This issue could be caused by JBEAP-6182 ([https://github.com/wildfly/wildfly-core/pull/1886/files]) > Following error is printed > {noformat} > Error: Could not find or load main class Files\ModCluster_Workspace\jboss-eap-7.1\standalone\log\gc.log > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8438) EJBComponentDescription : possible NPE on securityRoles

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-8438?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-8438: ----------------------------------- Fix Version/s: 11.0.0.Beta1 > EJBComponentDescription : possible NPE on securityRoles > ------------------------------------------------------- > > Key: WFLY-8438 > URL: https://issues.jboss.org/browse/WFLY-8438 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 11.0.0.Beta1 > > > In https://github.com/wildfly/wildfly/commit/38f8f5915b40d036bd0fd1a904d6a13... you added check on {{if (securityRoles != null)}}. > securityRoles is not checked few lines below your check (in different if block) > https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... (securityRoles.getSecurityRoleNamesByPrincipal ... ) > I suggest to change https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... from > {code} > if (runAsPrincipal != null) { > {code} > to > {code} > if ((securityRoles != null) && (runAsPrincipal != null)) { > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1503) Errors when parsing item definition allowed values are not reported

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1503?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1503: ------------------------------------- Assignee: Matteo Mortari (was: Edson Tirelli) > Errors when parsing item definition allowed values are not reported > ------------------------------------------------------------------- > > Key: DROOLS-1503 > URL: https://issues.jboss.org/browse/DROOLS-1503 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Matteo Mortari > Attachments: WrongConstraintsInItemDefinition.dmn > > > When validating or executing a DMN file that has something invalid in the allowedValues of an ItemDefinition, the compilation fails with no explanation. If you take the same expression and put it in the input/output values of a decision table, a message tells that this particular expression failed. > The attached example has [True,False] as the allowed value of the item definition, which is invalid and prevents model compilation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1503) Errors when parsing item definition allowed values are not reported

by Mélanie Gauthier (JIRA)

Mélanie Gauthier created DROOLS-1503: ---------------------------------------- Summary: Errors when parsing item definition allowed values are not reported Key: DROOLS-1503 URL: https://issues.jboss.org/browse/DROOLS-1503 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Mélanie Gauthier Assignee: Edson Tirelli Attachments: WrongConstraintsInItemDefinition.dmn When validating or executing a DMN file that has something invalid in the allowedValues of an ItemDefinition, the compilation fails with no explanation. If you take the same expression and put it in the input/output values of a decision table, a message tells that this particular expression failed. The attached example has [True,False] as the allowed value of the item definition, which is invalid and prevents model compilation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2433) Autocomplete doesn't work properly in credential-reference.store attribute.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2433?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2433: ------------------------------------- Fix Version/s: 3.0.0.Beta12 > Autocomplete doesn't work properly in credential-reference.store attribute. > --------------------------------------------------------------------------- > > Key: WFCORE-2433 > URL: https://issues.jboss.org/browse/WFCORE-2433 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Brian Stansberry > Fix For: 3.0.0.Beta12 > > > Autocomplete doesn't work properly in credential-reference attribute. > I want to use autocomplete for credential-reference.store but it doesn't work. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs1:add(uri="cr-store://test/cs1.jceks", credential-reference={store=<TAB> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2563) Missing failure description for incorrect module in Elytron dir-context

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2563?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2563: ------------------------------------- Fix Version/s: 3.0.0.Beta12 > Missing failure description for incorrect module in Elytron dir-context > ----------------------------------------------------------------------- > > Key: WFCORE-2563 > URL: https://issues.jboss.org/browse/WFCORE-2563 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta9 > Reporter: Ondrej Lukas > Assignee: ehsavoie Hugonnet > Labels: user_experience > Fix For: 3.0.0.Beta12 > > > In case when {{module}} attribute from Elytron {{dir-context}} includes module which does not exist, then insufficient failure description is provided - it only prints name of given module. It should rather inform that given module does not exist. > See: > {code} > /subsystem=elytron/dir-context=someDirContext:add(url=localhost,module=wrong.module) > { > "outcome" => "failed", > "failure-description" => "wrong.module", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2571) Enable OAUTH_BEARER SASL mechanism to CLI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2571?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-2571: ------------------------------------- Fix Version/s: 3.0.0.Beta12 > Enable OAUTH_BEARER SASL mechanism to CLI > ----------------------------------------- > > Key: WFCORE-2571 > URL: https://issues.jboss.org/browse/WFCORE-2571 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 3.0.0.Beta10 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 3.0.0.Beta12 > > > CLI should be able to support bearer token credentials in order to support integration with OAuth2 and OpenID Connect compliant authorization servers. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1256) To make JBOSS AS 7 node communication secure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1256?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1256: ---------------------------------------- Assignee: (was: Brian Stansberry) Unassigning from myself as I don't see having time to do this, and the elytron work is providing alternatives anyway. Hopefully the links from my last comment are useful > To make JBOSS AS 7 node communication secure > --------------------------------------------- > > Key: WFCORE-1256 > URL: https://issues.jboss.org/browse/WFCORE-1256 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Environment: JBOSS AS 7.1.0 final , Windows 7 > Reporter: hitesh yadav > Labels: jboss > > I am using JBOSS AS 7.1.0 final in domain mode . > There are 4 node in domain. > My requirement is to make node communication secure ............like HTTPS. > As per my understanding JBOSS AS 7 uses JGroups for communication between domain node and JGroups use TCP or UDP protocol for communicate. > For example ......when we are using HTTPS protocol, all communication between Browser and Server are done in Encrypted formate........... > I need same thing in JBOSS AS 7 node communication ........means all communication between domain nodes must be done in some Encryption/Decryption form or any other way to make communication secure ...... -- 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