March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1430) WARN logged during server shutdown when Elytron JACC is set

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1430?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1430: ---------------------------- Fix Version/s: 1.1.9.Final > WARN logged during server shutdown when Elytron JACC is set > ----------------------------------------------------------- > > Key: ELY-1430 > URL: https://issues.jboss.org/browse/ELY-1430 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.2.0.Beta8 > Reporter: Ondrej Kotek > Assignee: Ilia Vassilev > Priority: Critical > Fix For: 1.2.0.Beta11, 1.1.9.Final > > > When Elytron JACC policy resource is defined, there is WARN logged during server shutdown: > {{WARN [org.wildfly.security] (MSC service thread 1-8) ELY08509: Calling any of the Policy.getPermissions() methods is not supported; please see the Java Authorization Contract for Containers (JACC) specification (section "1.4 Requirements", item 1) and the Java SE API specification for the Policy.getPermissions() methods for more information. Instead, use the Policy.implies() method for authorization checking.}} > This is suspicious behaviour. Customers that monitor logs for warnings have to deal with this. Setting Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1430) WARN logged during server shutdown when Elytron JACC is set

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1430?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1430: ---------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/1028, https://github.com/wildfly-security/wildfly-elytron/pull/1107 (was: https://github.com/wildfly-security/wildfly-elytron/pull/1028) > WARN logged during server shutdown when Elytron JACC is set > ----------------------------------------------------------- > > Key: ELY-1430 > URL: https://issues.jboss.org/browse/ELY-1430 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.2.0.Beta8 > Reporter: Ondrej Kotek > Assignee: Ilia Vassilev > Priority: Critical > Fix For: 1.2.0.Beta11, 1.1.9.Final > > > When Elytron JACC policy resource is defined, there is WARN logged during server shutdown: > {{WARN [org.wildfly.security] (MSC service thread 1-8) ELY08509: Calling any of the Policy.getPermissions() methods is not supported; please see the Java Authorization Contract for Containers (JACC) specification (section "1.4 Requirements", item 1) and the Java SE API specification for the Policy.getPermissions() methods for more information. Instead, use the Policy.implies() method for authorization checking.}} > This is suspicious behaviour. Customers that monitor logs for warnings have to deal with this. Setting Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1428) Elytron provider has to be installed manually for key-store-ssl-certificate

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1428?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1428: ---------------------------- Fix Version/s: 1.1.9.Final > Elytron provider has to be installed manually for key-store-ssl-certificate > --------------------------------------------------------------------------- > > Key: ELY-1428 > URL: https://issues.jboss.org/browse/ELY-1428 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta11, 1.1.9.Final > > > Trying to configure ejb client 2-way TLS authentication with Elytron. I am getting "Invalid algorithm "clear" without use of programatically registering Elytron provider. > {noformat} > Security.addProvider(new WildFlyElytronProvider()); > {noformat} > Specifying this in {{wildfly-config.xml}} doesn't help: > {noformat} > <providers> > <use-service-loader/> > </providers> > {noformat} > Example of {{wildfly-config.xml}} where I need this when using it with EJB client: > {code:xml} > <configuration> > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="default"/> > </authentication-rules> > <authentication-configurations> > <configuration name="default"> > <credentials> > <key-store-reference key-store-name="client-keystore" alias="joe"> > <key-store-clear-password password="abcdef"/> > </key-store-reference> > </credentials> > </configuration> > </authentication-configurations> > <key-stores> > <key-store name="client-keystore" type="JKS"> > <file name="${keystore.path:src/main/resources/client.keystore}"/> > <key-store-clear-password password="abcdef"/> > </key-store> > <key-store name="client-truststore" type="JKS"> > <file name="${truststore.path:src/main/resources/client.truststore}"/> > </key-store> > </key-stores> > <ssl-contexts> > <ssl-context name="client-ssl-context"> > <trust-store key-store-name="client-truststore"/> > <key-store-ssl-certificate key-store-name="client-keystore" alias="joe"> > <key-store-clear-password password="abcdef"/> > </key-store-ssl-certificate> > </ssl-context> > </ssl-contexts> > <ssl-context-rules> > <rule use-ssl-context="client-ssl-context"/> > </ssl-context-rules> > </authentication-client> > </configuration> > {code} > Without installing the Elytron provider, the client will fail with this error: > {noformat} > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.wildfly.security.auth.client.AuthenticationContext.lambda$static$0(AuthenticationContext.java:49) > at org.wildfly.common.context.ContextManager.getPrivileged(ContextManager.java:282) > at org.wildfly.security.auth.client.AuthenticationContext.captureCurrent(AuthenticationContext.java:81) > at org.wildfly.naming.client.ProviderEnvironment$1.get(ProviderEnvironment.java:89) > at org.wildfly.naming.client.ProviderEnvironment$1.get(ProviderEnvironment.java:87) > at org.jboss.ejb.client.EJBClientInvocationContext.<init>(EJBClientInvocationContext.java:87) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:154) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:100) > at com.sun.proxy.$Proxy2.hello(Unknown Source) > at client.Client.main(Client.java:21) > Caused by: org.wildfly.security.auth.client.InvalidAuthenticationConfigurationException: org.wildfly.client.config.ConfigXMLParseException: ELY01135: Failed to load keystore data > at file:/home/jmartisk/Workspace/mock-artifacts/ejbclient/eap7.1-elytron-certificate-auth-with-two-way-ssl/client/target/classes/META-INF/wildfly-config.xml:9:87 > at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:40) > at java.security.AccessController.doPrivileged(Native Method) > at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.<clinit>(DefaultAuthenticationContextProvider.java:36) > ... 10 more > Caused by: org.wildfly.client.config.ConfigXMLParseException: ELY01135: Failed to load keystore data > at file:/home/jmartisk/Workspace/mock-artifacts/ejbclient/eap7.1-elytron-certificate-auth-with-two-way-ssl/client/target/classes/META-INF/wildfly-config.xml:9:87 > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$44(ElytronXmlParser.java:1410) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$28(ElytronXmlParser.java:952) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$26(ElytronXmlParser.java:939) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$36(ElytronXmlParser.java:997) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$21(ElytronXmlParser.java:733) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$26(ElytronXmlParser.java:939) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$25(ElytronXmlParser.java:781) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationRuleType$10(ElytronXmlParser.java:613) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$11(ElytronXmlParser.java:639) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:337) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:214) > at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:175) > at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38) > ... 12 more > Caused by: java.security.NoSuchAlgorithmException: ELY08028: Invalid algorithm "clear" > at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121) > at org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:75) > at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$44(ElytronXmlParser.java:1376) > ... 24 more > {noformat} > Using credential-store-reference clear-text cause similar error. > There is example of clear passwords which works, so it will be problem of this specific elements: > {code:xml} > <authentication-client xmlns="urn:elytron:1.0"> > <authentication-rules> > <rule use-configuration="default"/> > </authentication-rules> > <authentication-configurations> > <configuration name="default"> > <sasl-mechanism-selector selector="DIGEST-MD5"/> > <set-user-name name="joe"/> > <credentials> > <clear-password password="joeIsAwesome2013!"/> > </credentials> > </configuration> > </authentication-configurations> > </authentication-client> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1545) Release WildFly Elytron 1.1.9.Final

by Farah Juma (JIRA)

Farah Juma created ELY-1545: ------------------------------- Summary: Release WildFly Elytron 1.1.9.Final Key: ELY-1545 URL: https://issues.jboss.org/browse/ELY-1545 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3694) Upgrade WildFly Common to 1.3.1.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3694: ----------------------------------- Summary: Upgrade WildFly Common to 1.3.1.Final Key: WFCORE-3694 URL: https://issues.jboss.org/browse/WFCORE-3694 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Misc. small bug fixes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2156: --------------------------------------- In the properties channel, yes, but not on the navigator. > DMN decision table names should be presented as titles in editor screen. > ------------------------------------------------------------------------ > > Key: DROOLS-2156 > URL: https://issues.jboss.org/browse/DROOLS-2156 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Labels: UX > > To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2156: ------------------------------------- [~tirelli] Sounds good. For 1.1.1, would the description be provided in the properties panel? > DMN decision table names should be presented as titles in editor screen. > ------------------------------------------------------------------------ > > Key: DROOLS-2156 > URL: https://issues.jboss.org/browse/DROOLS-2156 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Labels: UX > > To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2397) PMML modules have classloader issues in OSGi

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2397?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2397: ------------------------------------- Assignee: Lance Leverich (was: Edson Tirelli) > PMML modules have classloader issues in OSGi > -------------------------------------------- > > Key: DROOLS-2397 > URL: https://issues.jboss.org/browse/DROOLS-2397 > Project: Drools > Issue Type: Bug > Affects Versions: 7.6.0.Final > Environment: Equinox OSGi container, Java 8 > Reporter: Jens Reimann > Assignee: Lance Leverich > > The drools PMML modules (drools-pmml and kie-pmml) both suffer from a few class loader issues when running inside an OSGi container. > The KieBase built for transforming the PMML model to Drools model selects the wrong class loader (based on the context class loader). The JAXB instance creator fails with the same problem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2156) DMN decision table names should be presented as titles in editor screen.

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2156?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2156: --------------------------------------- [~manstis] [~uxdlc] I don't think doing deeper levels in the navigation would be useful. Lets use 3 levels: 1. diagram name 1.1. node name 1.1.1 logic expression type (i.e., literal expression, decision table, etc) > DMN decision table names should be presented as titles in editor screen. > ------------------------------------------------------------------------ > > Key: DROOLS-2156 > URL: https://issues.jboss.org/browse/DROOLS-2156 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Labels: UX > > To help the user identify which table they are working on the name of the table should be presented in the editor view, as a page/table title. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3693) Upgrade WildFly Elytron Tool to 1.1.4.Final

by Farah Juma (JIRA)

Farah Juma created WFCORE-3693: ---------------------------------- Summary: Upgrade WildFly Elytron Tool to 1.1.4.Final Key: WFCORE-3693 URL: https://issues.jboss.org/browse/WFCORE-3693 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 March 2018