February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1958) Clean up testsuite Elytron registration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1958?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1958: ------------------------------------------ https://github.com/wildfly/wildfly-core/pull/2218 reenables the last @Ignored test, since it passes for me locally. > Clean up testsuite Elytron registration > --------------------------------------- > > Key: WFCORE-1958 > URL: https://issues.jboss.org/browse/WFCORE-1958 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta7 > > > In a couple of places we have artificially registered the WildFly Elytron Security provider, we need to address this so tests can automatically have it available to them.. > Also re-enable the following test case: - > * org.jboss.as.test.integration.domain.suites.FullRbacProviderRunAsTestSuite -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8023) Autocomplete doesn't work properly in credential-reference.alias attribute.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8023?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-8023: ----------------------------------- Issue Type: Enhancement (was: Bug) This is not information available to the CLI via any standard tab completion mechanism and thus is an RFE. > Autocomplete doesn't work properly in credential-reference.alias attribute. > --------------------------------------------------------------------------- > > Key: WFLY-8023 > URL: https://issues.jboss.org/browse/WFLY-8023 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > Autocomplete doesn't work properly in credential-reference.alias attribute. > I want to use autocomplete for credential-reference.alias when I the credential-reference.store attribute is filled but it doesn't work. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs1:add(uri="cr-store://test/cs1.jceks", credential-reference={store=cs012, alias=<TAB> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3759) Make IP address of remote EJB client accessible to the developer from within app authentication code

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3759?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3759: ----------------------------------- Component/s: EJB (was: Domain Management) > Make IP address of remote EJB client accessible to the developer from within app authentication code > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3759 > URL: https://issues.jboss.org/browse/WFLY-3759 > Project: WildFly > Issue Type: Feature Request > Components: EJB, Security > Reporter: Derek Horton > Assignee: Darran Lofthouse > > Make the IP address of remote EJB clients accessible from within a login module login module when the security-realm is configured to defer to JAAS. > This is possible when the authentication is handled by the security-realm, but it is not possible when the security-realm defers to a security-domain (JAAS). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2346) Revisit enforcement of required file system permissions.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2346?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-431 to WFCORE-2346: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-2346 (was: WFLY-431) Component/s: Domain Management (was: Domain Management) > Revisit enforcement of required file system permissions. > -------------------------------------------------------- > > Key: WFCORE-2346 > URL: https://issues.jboss.org/browse/WFCORE-2346 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > > Now that AS8 has moved to Java 7 we can re-visit the level of control we have over file system permissions, this can be from taking more control of the local authentication mechanism to ensure incorrect permissions are not inherited to verifying sensitive configuration files are not world readable. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1457) Guided rules editor function field does not perform semantic validation

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1457?page=com.atlassian.jira.plugi... ] Petr Široký reassigned DROOLS-1457: ----------------------------------- Assignee: (was: Petr Široký) > Guided rules editor function field does not perform semantic validation > ----------------------------------------------------------------------- > > Key: DROOLS-1457 > URL: https://issues.jboss.org/browse/DROOLS-1457 > Project: Drools > Issue Type: Feature Request > Reporter: Kalyan gogineni > > guided rules editor function field does not perform semantic validation. > For example: when you define rules like below > When number 1 is not null > And number 2 is not null > Then number 3 = number5/number1 > Note: Where number5 is not defined. Then when you compile or build and deploy then drools does not throw error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1457) Guided rules editor function field does not perform semantic validation

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1457?page=com.atlassian.jira.plugi... ] Petr Široký updated DROOLS-1457: -------------------------------- Component/s: (was: build) > Guided rules editor function field does not perform semantic validation > ----------------------------------------------------------------------- > > Key: DROOLS-1457 > URL: https://issues.jboss.org/browse/DROOLS-1457 > Project: Drools > Issue Type: Feature Request > Reporter: Kalyan gogineni > Assignee: Petr Široký > > guided rules editor function field does not perform semantic validation. > For example: when you define rules like below > When number 1 is not null > And number 2 is not null > Then number 3 = number5/number1 > Note: Where number5 is not defined. Then when you compile or build and deploy then drools does not throw error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1457) Guided rules editor function field does not perform semantic validation

by Kalyan gogineni (JIRA)

Kalyan gogineni created DROOLS-1457: --------------------------------------- Summary: Guided rules editor function field does not perform semantic validation Key: DROOLS-1457 URL: https://issues.jboss.org/browse/DROOLS-1457 Project: Drools Issue Type: Feature Request Components: build Reporter: Kalyan gogineni Assignee: Petr Široký guided rules editor function field does not perform semantic validation. For example: when you define rules like below When number 1 is not null And number 2 is not null Then number 3 = number5/number1 Note: Where number5 is not defined. Then when you compile or build and deploy then drools does not throw error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1456) Improve error messages and error handling on DMN compilation and execution

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-1456: ------------------------------------- Summary: Improve error messages and error handling on DMN compilation and execution Key: DROOLS-1456 URL: https://issues.jboss.org/browse/DROOLS-1456 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.0.0.Beta6 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.0.0.Final This is a placeholder ticket for several small improvements on the error messages and error handling. 1. When a decision or a BKM has no expression, it raises the message “No expression defined for node ‘_guid’”. Would it be possible to put the node name when one is defined instead? 2. etc -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8254) Changing sasl-authentication-factory in management interface ends in reload-required state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8254?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-8254: ---------------------------------------- Please file bugs against kernel resources in WFCORE. > Changing sasl-authentication-factory in management interface ends in reload-required state > ------------------------------------------------------------------------------------------ > > Key: WFLY-8254 > URL: https://issues.jboss.org/browse/WFLY-8254 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > > Attribute sasl-authentication-factory is described as follows > {code} > "sasl-authentication-factory" => { > "type" => STRING, > "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.security.sasl-authentication-factory", > "min-length" => 1L, > "max-length" => 2147483647L > } > {code} > Documenation [1] says: > no-services – Applying the operation to the runtime does not require the restart of any services. This value is the default if the restart-required descriptor is not present. > But when I try to change it I get: > {code} > [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=application-sasl-authentication) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Probably some proper value for "restart-required" should be used. "restart-required" => "all-services" ? > [1] https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2345) Changing sasl-authentication-factory in management interface ends in reload-required state

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2345?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8254 to WFCORE-2345: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2345 (was: WFLY-8254) Component/s: Domain Management Security (was: Security) > Changing sasl-authentication-factory in management interface ends in reload-required state > ------------------------------------------------------------------------------------------ > > Key: WFCORE-2345 > URL: https://issues.jboss.org/browse/WFCORE-2345 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > > Attribute sasl-authentication-factory is described as follows > {code} > "sasl-authentication-factory" => { > "type" => STRING, > "description" => "The server side SASL authentication policy to use to secure the interface where the connection is after a HTTP upgrade.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.security.sasl-authentication-factory", > "min-length" => 1L, > "max-length" => 2147483647L > } > {code} > Documenation [1] says: > no-services – Applying the operation to the runtime does not require the restart of any services. This value is the default if the restart-required descriptor is not present. > But when I try to change it I get: > {code} > [standalone@localhost:9990 /] /core-service=management/management-interface=http-interface:write-attribute(name=http-upgrade.sasl-authentication-factory, value=application-sasl-authentication) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {code} > Probably some proper value for "restart-required" should be used. "restart-required" => "all-services" ? > [1] https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

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