February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1418) Binding of List stored in Map doesn't work in special case

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1418?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1418. --------------------------------- Fix Version/s: 7.0.0.CR1 Resolution: Done Fixed on mvel with this commit https://github.com/mvel/mvel/commit/7f247cd6018cbb9d6a5b5c07e3b1ba7e770cb205 > Binding of List stored in Map doesn't work in special case > ---------------------------------------------------------- > > Key: DROOLS-1418 > URL: https://issues.jboss.org/browse/DROOLS-1418 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Mario Fusco > Labels: dtable_testday_preparation, reported-by-qe > Fix For: 7.0.0.CR1 > > Attachments: reproducer.zip > > > User has possibility to bind a List stored as item of a Map in his rule. However this dosn't work in one special case. For more details see the steps to reproduce. > This issue was discussed with [~tari_manga] and he also provided the workaround used in reproducer. Thanks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8012) Elytron kerberos-security-factory debug attribute type

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-8012?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFLY-8012: ------------------------------- Labels: user_experience (was: UserExperience) > Elytron kerberos-security-factory debug attribute type > ------------------------------------------------------ > > Key: WFLY-8012 > URL: https://issues.jboss.org/browse/WFLY-8012 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Darran Lofthouse > Labels: user_experience > > Currently kerberos-security-factory debug attribute is in management model defined as STRING type, but could be BOOLEAN. > {code} > "kerberos-security-factory" => { > "description" => "A security factory for obtaining a GSSCredential for use during authentication.", > "model-description" => {"*" => { > "description" => "A security factory for obtaining a GSSCredential for use during authentication.", > "capabilities" => [{ > "name" => "org.wildfly.security.security-factory.credential", > "dynamic" => true > }], > "attributes" => { > "debug" => { > "type" => STRING, > "description" => "Should the JAAS step of obtaining the credential have debug logging enabled.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => false, > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > {code} > In XSD it is properly configured as boolean > {code:xml} > <xs:attribute name="debug" type="xs:boolean" default="false"> > <xs:annotation> > <xs:documentation> > Should the JAAS step of obtaining the credential have debug logging enabled. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8012) Elytron kerberos-security-factory debug attribute type

by Martin Choma (JIRA)

Martin Choma created WFLY-8012: ---------------------------------- Summary: Elytron kerberos-security-factory debug attribute type Key: WFLY-8012 URL: https://issues.jboss.org/browse/WFLY-8012 Project: WildFly Issue Type: Bug Components: Security Reporter: Martin Choma Assignee: Darran Lofthouse Currently kerberos-security-factory debug attribute is in management model defined as STRING type, but could be BOOLEAN. {code} "kerberos-security-factory" => { "description" => "A security factory for obtaining a GSSCredential for use during authentication.", "model-description" => {"*" => { "description" => "A security factory for obtaining a GSSCredential for use during authentication.", "capabilities" => [{ "name" => "org.wildfly.security.security-factory.credential", "dynamic" => true }], "attributes" => { "debug" => { "type" => STRING, "description" => "Should the JAAS step of obtaining the credential have debug logging enabled.", "expressions-allowed" => true, "required" => false, "nillable" => true, "default" => false, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "resource-services" }, {code} In XSD it is properly configured as boolean {code:xml} <xs:attribute name="debug" type="xs:boolean" default="false"> <xs:annotation> <xs:documentation> Should the JAAS step of obtaining the credential have debug logging enabled. </xs:documentation> </xs:annotation> </xs:attribute> {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8011) Remove Ignored tests from EarModulesPPTestCase

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8011?page=com.atlassian.jira.plugin.... ] Josef Cacek updated WFLY-8011: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/9589 > Remove Ignored tests from EarModulesPPTestCase > ---------------------------------------------- > > Key: WFLY-8011 > URL: https://issues.jboss.org/browse/WFLY-8011 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > The related issue JBEAP-411/WFLY-4886 was rejected so the tests don't check expected behavior. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-908) Fix LegacyPropertiesSecurityRealmTest

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-908?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas updated ELY-908: ----------------------------- Description: {{specialchars.properties}} uses wrong encoding which results to test failures. > Fix LegacyPropertiesSecurityRealmTest > ------------------------------------- > > Key: ELY-908 > URL: https://issues.jboss.org/browse/ELY-908 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > Priority: Minor > > {{specialchars.properties}} uses wrong encoding which results to test failures. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-908) Fix LegacyPropertiesSecurityRealmTest

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-908: -------------------------------- Summary: Fix LegacyPropertiesSecurityRealmTest Key: ELY-908 URL: https://issues.jboss.org/browse/ELY-908 Project: WildFly Elytron Issue Type: Bug Components: Testsuite Affects Versions: 1.1.0.Beta21 Reporter: Ondrej Lukas Assignee: Ondrej Lukas Priority: Minor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8011) Remove Ignored tests from EarModulesPPTestCase

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8011: --------------------------------- Summary: Remove Ignored tests from EarModulesPPTestCase Key: WFLY-8011 URL: https://issues.jboss.org/browse/WFLY-8011 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Josef Cacek The related issue JBEAP-411/WFLY-4886 was rejected so the tests don't check expected behavior. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8011) Remove Ignored tests from EarModulesPPTestCase

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8011?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-8011: --------------------------------- Assignee: Josef Cacek > Remove Ignored tests from EarModulesPPTestCase > ---------------------------------------------- > > Key: WFLY-8011 > URL: https://issues.jboss.org/browse/WFLY-8011 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > The related issue JBEAP-411/WFLY-4886 was rejected so the tests don't check expected behavior. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6573) Allow Vault encrypted strings to be updated without a restart

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6573: ----------------------------------- Comment: was deleted (was: Customer Allianz Managed Operations & Services SE would like this feature to be implemented.) > Allow Vault encrypted strings to be updated without a restart > ------------------------------------------------------------- > > Key: WFLY-6573 > URL: https://issues.jboss.org/browse/WFLY-6573 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 10.0.0.Final > Reporter: Brad Maxwell > Assignee: Darran Lofthouse > > When a new vault string is created the affected servers in the domain have to be restarted before the encrypted value is applied. This makes it difficult to test a new configuration in CLI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-907) LdapRealm - different principal/credential for referrals

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-907?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-907: --------------------------- Description: When LdapRealm follows referrals, it uses the original context's environment properties, including principal/credential, to create a connection to the referred server. Sometimes you might want to follow the referral using different authentication information. This can be done when using AuthenticationContext. Note: how to pass different credentials into referred DirContext: http://www.cs.binghamton.edu/~steflik/cs328/jndi/tutorial/ldap/referral/t... (part Authenticating to a Referral Context) was: When LdapRealm follows referrals, it uses the original context's environment properties, including principal/credential, to create a connection to the referred server. Sometimes you might want to follow the referral using different authentication information. This can be done using AuthenticationContext by following way: http://www.cs.binghamton.edu/~steflik/cs328/jndi/tutorial/ldap/referral/t... (part Authenticating to a Referral Context) > LdapRealm - different principal/credential for referrals > -------------------------------------------------------- > > Key: ELY-907 > URL: https://issues.jboss.org/browse/ELY-907 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > When LdapRealm follows referrals, it uses the original context's environment properties, including principal/credential, to create a connection to the referred server. Sometimes you might want to follow the referral using different authentication information. > This can be done when using AuthenticationContext. > Note: how to pass different credentials into referred DirContext: > http://www.cs.binghamton.edu/~steflik/cs328/jndi/tutorial/ldap/referral/t... (part Authenticating to a Referral Context) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 February 2017