September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1720) Cannot both perform an explicit updateToVersion on a KieContainer and use a KieScanner on it

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1720?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1720: ------------------------------------- Also the following commits are necessary for this fix https://github.com/kiegroup/drools/commit/009aa4210c9c4b6e52d9b662dce2148... https://github.com/kiegroup/droolsjbpm-integration/commit/51251b86c98db75... > Cannot both perform an explicit updateToVersion on a KieContainer and use a KieScanner on it > -------------------------------------------------------------------------------------------- > > Key: DROOLS-1720 > URL: https://issues.jboss.org/browse/DROOLS-1720 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 8.0.0.Beta1 > > Attachments: 01917714test.zip > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1360) Review FileSystemRealm XML Types

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1360: ------------------------------------- Summary: Review FileSystemRealm XML Types Key: ELY-1360 URL: https://issues.jboss.org/browse/ELY-1360 Project: WildFly Elytron Issue Type: Task Components: Realms Reporter: Darran Lofthouse Fix For: 1.2.0.Beta4 Ideally if we can achieve a type system that allows older clients to still make use of the entry for an identity even if some aspects of the later config it does not understand. The filesystem realm is complicated further in that the older version may wish to make updates so we would also need to consider some form of generically persisting the XML not understood but at the same time we don't know if the portion not understood relates to the current update. The later version may also need to compensate for this in some way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1724) DRL compilation error on a generic type property

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1724?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-1724: ------------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > DRL compilation error on a generic type property > ------------------------------------------------ > > Key: DROOLS-1724 > URL: https://issues.jboss.org/browse/DROOLS-1724 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final > Environment: drools 6.5.0.Final / java 1.8.0_131 > Reporter: Ryo Murai > Assignee: Mario Fusco > > I got a DRL compilation error on accessing through a generic type property. Minimized object definition is below. > {code:borderStyle=solid} > public interface OrderLine<T extends Product> { > T getProduct(); > } > public interface Product { > String getId(); > String getCategory(); > } > // and I have concrete classes, ex. Book, BookOrderLine<Book>, DVD, DVDOrderLine<DVD>, ... etc > {code} > DRL(snippet) is here > {code:borderStyle=solid} > when > $orderLine: OrderLine() > // compilation failed > Product( > id == $orderLine.product.id || category == $orderLine.product.category > ) from discountProducts > {code} > This causes below exception. > {panel} > java.lang.RuntimeException: [Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules/checkorder-not-compiled.drl, line=15, column=0 text=Unable to Analyse Expression id == $orderLine.product.id || category == $orderLine.product.category: > [Error: unable to resolve method using strict-mode: java.lang.Object.category()] > [Near : {... Line.product.id || category == $orderLine.product.category ....}] > ^ > [Line: 15, Column: 2]]] > {panel} > This is weird because it won't occur when the restriction has single condition like below. Drools could analyze this expression. > {code:borderStyle=solid} > when > $orderLine: OrderLine() > // this is compiled, even if `Product(id == $orderLine.product.id)` > Product( > category == $orderLine.product.category > ) from discountProducts > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1359) Mask password when logging LDAP connection environment

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1359?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev reassigned ELY-1359: ---------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Mask password when logging LDAP connection environment > ------------------------------------------------------ > > Key: ELY-1359 > URL: https://issues.jboss.org/browse/ELY-1359 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Critical > > When TRACE logging is set there is password logged into log. > {code} > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Creating [class javax.naming.directory.InitialDirContext] with environment: > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.security.credentials] with value [[s, e, c, r, e, t]] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.ldap.factory.socket] with value [org.wildfly.security.auth.realm.ldap.ThreadLocalSSLSocketFactory] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.security.authentication] with value [simple] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.provider.url] with value [ldaps://localhost.localdomain:15636 ldaps://localhost.localdomain:15637 ldaps://localhost.localdomain:15638] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [com.sun.jndi.ldap.read.timeout] with value [60000] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [com.sun.jndi.ldap.connect.pool] with value [false] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [com.sun.jndi.ldap.connect.timeout] with value [5000] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.security.principal] with value [uid=admin,ou=system] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.referral] with value [ignore] > 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.factory.initial] with value [com.sun.jndi.ldap.LdapCtxFactory] > {code} > There was similar PicketBox issue in past based on customer request[1] > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1020663 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1359) Mask password when logging LDAP connection environment

by Martin Choma (JIRA)

Martin Choma created ELY-1359: --------------------------------- Summary: Mask password when logging LDAP connection environment Key: ELY-1359 URL: https://issues.jboss.org/browse/ELY-1359 Project: WildFly Elytron Issue Type: Bug Reporter: Martin Choma Assignee: Darran Lofthouse Priority: Critical When TRACE logging is set there is password logged into log. {code} 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Creating [class javax.naming.directory.InitialDirContext] with environment: 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.security.credentials] with value [[s, e, c, r, e, t]] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.ldap.factory.socket] with value [org.wildfly.security.auth.realm.ldap.ThreadLocalSSLSocketFactory] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.security.authentication] with value [simple] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.provider.url] with value [ldaps://localhost.localdomain:15636 ldaps://localhost.localdomain:15637 ldaps://localhost.localdomain:15638] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [com.sun.jndi.ldap.read.timeout] with value [60000] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [com.sun.jndi.ldap.connect.pool] with value [false] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [com.sun.jndi.ldap.connect.timeout] with value [5000] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.security.principal] with value [uid=admin,ou=system] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.referral] with value [ignore] 14:41:28,701 DEBUG [org.wildfly.security] (default task-36) Property [java.naming.factory.initial] with value [com.sun.jndi.ldap.LdapCtxFactory] {code} There was similar PicketBox issue in past based on customer request[1] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1020663 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1358) Elytron properties-realm enforces REALM_NAME comment

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1358?page=com.atlassian.jira.plugin.s... ] Jan Kalina resolved ELY-1358. ----------------------------- Fix Version/s: 1.2.0.Beta3 Resolution: Duplicate Issue > Elytron properties-realm enforces REALM_NAME comment > ---------------------------------------------------- > > Key: ELY-1358 > URL: https://issues.jboss.org/browse/ELY-1358 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Reporter: Josef Cacek > Assignee: Jan Kalina > Fix For: 1.2.0.Beta3 > > > Elytron enforces existence of {{"#$REALM_NAME=...$"}} comment in property file referenced from properties-realms. > When using legacy security and this line is missing, server starts without error. > *Expected behavior:* > Elytron's properties-realm *doesn't require* this comment. If the comment is present, it *may* verify if its content fits the realm name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1358) Elytron properties-realm enforces REALM_NAME comment

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1358?page=com.atlassian.jira.plugin.s... ] Jan Kalina moved WFCORE-2416 to ELY-1358: ----------------------------------------- Project: WildFly Elytron (was: WildFly Core) Key: ELY-1358 (was: WFCORE-2416) Component/s: Realms (was: Security) > Elytron properties-realm enforces REALM_NAME comment > ---------------------------------------------------- > > Key: ELY-1358 > URL: https://issues.jboss.org/browse/ELY-1358 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Reporter: Josef Cacek > Assignee: Jan Kalina > > Elytron enforces existence of {{"#$REALM_NAME=...$"}} comment in property file referenced from properties-realms. > When using legacy security and this line is missing, server starts without error. > *Expected behavior:* > Elytron's properties-realm *doesn't require* this comment. If the comment is present, it *may* verify if its content fits the realm name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1357) GSSCredential CredentialSource (local-kerberos) into XML

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1357?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1357: --------------------------------- For needs of testing: usage is described at https://honza889.github.io/2017/08/16/kerberos/#testing > GSSCredential CredentialSource (local-kerberos) into XML > -------------------------------------------------------- > > Key: ELY-1357 > URL: https://issues.jboss.org/browse/ELY-1357 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credentials > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > Initially this should be minimal / no configuration to make a GSSCrdential available if the local user has a Kerberos ticket - at a later point we can review adding additional config such as client keytabs etc... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1066) Add a GSSCredential CredentialSource

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1066?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1066: --------------------------------- Integration into XML config moved into ELY-1357 > Add a GSSCredential CredentialSource > ------------------------------------ > > Key: ELY-1066 > URL: https://issues.jboss.org/browse/ELY-1066 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credentials > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Fix For: 1.2.0.Beta2 > > > Initially this should be minimal / no configuration to make a GSSCrdential available if the local user has a Kerberos ticket - at a later point we can review adding additional config such as client keytabs etc... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1357) GSSCredential CredentialSource (local-kerberos) into XML

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1357?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1357: ---------------------------- Fix Version/s: (was: 1.2.0.Beta2) > GSSCredential CredentialSource (local-kerberos) into XML > -------------------------------------------------------- > > Key: ELY-1357 > URL: https://issues.jboss.org/browse/ELY-1357 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Credentials > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > > Initially this should be minimal / no configuration to make a GSSCrdential available if the local user has a Kerberos ticket - at a later point we can review adding additional config such as client keytabs etc... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 September 2017