[JBoss JIRA] (ELY-1254) Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-1254?page=com.atlassian.jira.plugin.s... ]
Pedro Igor resolved ELY-1254.
-----------------------------
Fix Version/s: 1.1.0.Beta54
Resolution: Out of Date
> Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used
> ------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1254
> URL: https://issues.jboss.org/browse/ELY-1254
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
> Fix For: 1.1.0.Beta54
>
>
> When Elytron client configuration file includes configuration.authentication-client.authentication-configurations.configuration.credentials.key-store-reference element then ConfigXMLParseException is thrown during parsing of configuration file. This issue can be caused by JBEAP-11691.
> For following configuration file:
> {code}
> <configuration>
> <authentication-client xmlns="urn:elytron:1.0">
> <authentication-rules>
> <rule use-configuration="default"/>
> </authentication-rules>
> <authentication-configurations>
> <configuration name="default">
> <sasl-mechanism-selector selector="PLAIN"/>
> <credentials>
> <key-store-reference key-store-name="clientKeyStore">
> <key-store-clear-password password="secret"/>
> </key-store-reference>
> </credentials>
> <providers>
> <use-service-loader/>
> </providers>
> </configuration>
> </authentication-configurations>
> <key-stores>
> <key-store name="clientKeyStore" type="JKS">
> <file name="/path/to/some/client.keystore"/>
> <key-store-clear-password password="secretKeyStore"/>
> </key-store>
> </key-stores>
> </authentication-client>
> </configuration>
> {code}
> following exception is thrown:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: ELY01135: Failed to load keystore data
> at file:/path/to/some/wildfly-config.xml:10:74
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$41(ElytronXmlParser.java:1448)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$25(ElytronXmlParser.java:932)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$35(ElytronXmlParser.java:986)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$18(ElytronXmlParser.java:715)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$22(ElytronXmlParser.java:763)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationRuleType$7(ElytronXmlParser.java:599)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$8(ElytronXmlParser.java:623)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:323)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:185)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:146)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 18 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$41(ElytronXmlParser.java:1423)
> ... 30 more
> {code}
> It seems that mentioned configuration file does not result to ConfigXMLParseException in EAP 7.1.0.DR19.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity
by Nuno Godinho de Matos (JIRA)
[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ]
Nuno Godinho de Matos commented on WFLY-8954:
---------------------------------------------
Hi,
Has anyone been able to verify the problem with on success observing CDI events leading to business logic running with stale data entities?
Because of this, several code spots need to be refactored in a normal application to postpone the handling of the onsuccess onto a new transaction that may only take place one the life cycle of of the business logic that triggered the on success is finished. This leads to a lot of additional effort.
Many thanks.
> Wildfly 10 with eclipselink Onscucess observer gets stale entity
> ----------------------------------------------------------------
>
> Key: WFLY-8954
> URL: https://issues.jboss.org/browse/WFLY-8954
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Nuno Godinho de Matos
>
> Hi,
> In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink.
> When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success.
> Then the observer will be working with stale entities that do not reflect the modifications done to the entity.
> A sample application for this issue is available in:
> https://github.com/99sono/wildfly10-observe-on-success-stale-entity
> The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation.
> Many thanks for taking a look.
> Kindest regards.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1254) Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-1254?page=com.atlassian.jira.plugin.s... ]
Pedro Igor commented on ELY-1254:
---------------------------------
This seems to be fixed by https://issues.jboss.org/browse/ELY-1238.
> Elytron client configuration file throws ConfigXMLParseException when credential key-store-reference is used
> ------------------------------------------------------------------------------------------------------------
>
> Key: ELY-1254
> URL: https://issues.jboss.org/browse/ELY-1254
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
>
> When Elytron client configuration file includes configuration.authentication-client.authentication-configurations.configuration.credentials.key-store-reference element then ConfigXMLParseException is thrown during parsing of configuration file. This issue can be caused by JBEAP-11691.
> For following configuration file:
> {code}
> <configuration>
> <authentication-client xmlns="urn:elytron:1.0">
> <authentication-rules>
> <rule use-configuration="default"/>
> </authentication-rules>
> <authentication-configurations>
> <configuration name="default">
> <sasl-mechanism-selector selector="PLAIN"/>
> <credentials>
> <key-store-reference key-store-name="clientKeyStore">
> <key-store-clear-password password="secret"/>
> </key-store-reference>
> </credentials>
> <providers>
> <use-service-loader/>
> </providers>
> </configuration>
> </authentication-configurations>
> <key-stores>
> <key-store name="clientKeyStore" type="JKS">
> <file name="/path/to/some/client.keystore"/>
> <key-store-clear-password password="secretKeyStore"/>
> </key-store>
> </key-stores>
> </authentication-client>
> </configuration>
> {code}
> following exception is thrown:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: ELY01135: Failed to load keystore data
> at file:/path/to/some/wildfly-config.xml:10:74
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$41(ElytronXmlParser.java:1448)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$25(ElytronXmlParser.java:932)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseCredentialsType$35(ElytronXmlParser.java:986)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$18(ElytronXmlParser.java:715)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$andThenOp$23(ElytronXmlParser.java:919)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationConfigurationType$22(ElytronXmlParser.java:763)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationRuleType$7(ElytronXmlParser.java:599)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseRulesType$8(ElytronXmlParser.java:623)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:323)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:185)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:146)
> at org.wildfly.security.auth.client.DefaultAuthenticationContextProvider.lambda$static$0(DefaultAuthenticationContextProvider.java:38)
> ... 18 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$41(ElytronXmlParser.java:1423)
> ... 30 more
> {code}
> It seems that mentioned configuration file does not result to ConfigXMLParseException in EAP 7.1.0.DR19.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1248) Elytron client configuration file throws ConfigXMLParseException when crypt-password is used
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-1248?page=com.atlassian.jira.plugin.s... ]
Pedro Igor resolved ELY-1248.
-----------------------------
Fix Version/s: 1.1.0.Beta54
Resolution: Out of Date
> Elytron client configuration file throws ConfigXMLParseException when crypt-password is used
> --------------------------------------------------------------------------------------------
>
> Key: ELY-1248
> URL: https://issues.jboss.org/browse/ELY-1248
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
> Fix For: 1.1.0.Beta54
>
>
> When Elytron client configuration file includes {{configuration.authentication-client.authentication-configurations.configuration.credentials.crypt-password}} element then ConfigXMLParseException is thrown during parsing of configuration file. It seems it is caused by {{$}} char in crypt value. It does not work even if this symbol is escaped.
> For following configuration file:
> {code}
> <configuration>
> <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"/>
> <credentials>
> <crypt-password crypt="$1$somesalt$W.KCTbPSiFDGffAGOjcBc."/>
> </credentials>
> </configuration>
> </authentication-configurations>
> </authentication-client>
> </configuration>
> {code}
> following exception is thrown:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: CONF0020: Failed to parse expression value of attribute "crypt"
> at org.wildfly.common.expression.Expression.invalidExpressionSyntax(Expression.java:659)
> at org.wildfly.common.expression.Expression.parseString(Expression.java:509)
> at org.wildfly.common.expression.Expression.compile(Expression.java:203)
> at org.wildfly.common.expression.Expression.compile(Expression.java:183)
> at org.wildfly.client.config.ConfigurationXMLStreamReader.getExpressionAttributeValue(ConfigurationXMLStreamReader.java:683)
> at org.wildfly.client.config.ConfigurationXMLStreamReader.getAttributeValueResolved(ConfigurationXMLStreamReader.java:330)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$requireSingleAttribute$44(ElytronXmlParser.java:2361)
> at org.wildfly.security.auth.client.ElytronXmlParser.requireSingleAttribute(ElytronXmlParser.java:2380)
> at org.wildfly.security.auth.client.ElytronXmlParser.requireSingleAttribute(ElytronXmlParser.java:2361)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseCryptPassword(ElytronXmlParser.java:1059)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseCredentialsType(ElytronXmlParser.java:951)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationConfigurationType(ElytronXmlParser.java:714)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationConfigurationsType(ElytronXmlParser.java:341)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:273)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:185)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:164)
> ...
> {code}
> It does not work even if dollar sign is escaped:
> {code}
> <crypt-password crypt="\$1\$somesalt\$W.KCTbPSiFDGffAGOjcBc."/>
> {code}
> Value of crypt was created in the same way as in UnixMD5CryptUtilTest [1].
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/371c1334fde7527d...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1247) Elytron client configuration file throws ConfigXMLParseException when hashed-password is used
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-1247?page=com.atlassian.jira.plugin.s... ]
Pedro Igor resolved ELY-1247.
-----------------------------
Fix Version/s: 1.1.0.Beta54
Resolution: Out of Date
> Elytron client configuration file throws ConfigXMLParseException when hashed-password is used
> ---------------------------------------------------------------------------------------------
>
> Key: ELY-1247
> URL: https://issues.jboss.org/browse/ELY-1247
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
> Fix For: 1.1.0.Beta54
>
>
> When Elytron client configuration file includes {{configuration.authentication-client.authentication-configurations.configuration.credentials.hashed-password}} element then ConfigXMLParseException is thrown during parsing of configuration file.
> For following configuration file:
> {code}
> <configuration>
> <authentication-client xmlns="urn:elytron:1.0">
> <authentication-rules>
> <rule use-configuration="auth-config"/>
> </authentication-rules>
> <authentication-configurations>
> <configuration name="auth-config">
> <sasl-mechanism-selector selector="DIGEST-MD5"/>
> <set-user-name name="user"/>
> <credentials>
> <hashed-password algorithm="simple-digest-md5" hash="cGFzc3dvcmQ="/>
> </credentials>
> </configuration>
> </authentication-configurations>
> </authentication-client>
> </configuration>
> {code}
> following exception is thrown:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: CONF0005: Unexpected element "authentication-client" in namespace "urn:elytron:1.0" encountered
> at vfs:/content/wildfly-config-xml.war/META-INF/wildfly-config.xml:15:5
> at org.wildfly.client.config.ConfigurationXMLStreamReader.unexpectedElement(ConfigurationXMLStreamReader.java:245)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:197)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:146)
> at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
> ... 41 more
> {code}
> When {{hashed-password}} is changed to {{clear-password}}:
> {code}
> <clear-password password="password"/>
> {code}
> then it is parsed correctly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1248) Elytron client configuration file throws ConfigXMLParseException when crypt-password is used
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-1248?page=com.atlassian.jira.plugin.s... ]
Pedro Igor commented on ELY-1248:
---------------------------------
Can we close this one as it seems to not be a issue anymore due to https://issues.jboss.org/browse/ELY-1252 ?
> Elytron client configuration file throws ConfigXMLParseException when crypt-password is used
> --------------------------------------------------------------------------------------------
>
> Key: ELY-1248
> URL: https://issues.jboss.org/browse/ELY-1248
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
>
> When Elytron client configuration file includes {{configuration.authentication-client.authentication-configurations.configuration.credentials.crypt-password}} element then ConfigXMLParseException is thrown during parsing of configuration file. It seems it is caused by {{$}} char in crypt value. It does not work even if this symbol is escaped.
> For following configuration file:
> {code}
> <configuration>
> <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"/>
> <credentials>
> <crypt-password crypt="$1$somesalt$W.KCTbPSiFDGffAGOjcBc."/>
> </credentials>
> </configuration>
> </authentication-configurations>
> </authentication-client>
> </configuration>
> {code}
> following exception is thrown:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: CONF0020: Failed to parse expression value of attribute "crypt"
> at org.wildfly.common.expression.Expression.invalidExpressionSyntax(Expression.java:659)
> at org.wildfly.common.expression.Expression.parseString(Expression.java:509)
> at org.wildfly.common.expression.Expression.compile(Expression.java:203)
> at org.wildfly.common.expression.Expression.compile(Expression.java:183)
> at org.wildfly.client.config.ConfigurationXMLStreamReader.getExpressionAttributeValue(ConfigurationXMLStreamReader.java:683)
> at org.wildfly.client.config.ConfigurationXMLStreamReader.getAttributeValueResolved(ConfigurationXMLStreamReader.java:330)
> at org.wildfly.security.auth.client.ElytronXmlParser.lambda$requireSingleAttribute$44(ElytronXmlParser.java:2361)
> at org.wildfly.security.auth.client.ElytronXmlParser.requireSingleAttribute(ElytronXmlParser.java:2380)
> at org.wildfly.security.auth.client.ElytronXmlParser.requireSingleAttribute(ElytronXmlParser.java:2361)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseCryptPassword(ElytronXmlParser.java:1059)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseCredentialsType(ElytronXmlParser.java:951)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationConfigurationType(ElytronXmlParser.java:714)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationConfigurationsType(ElytronXmlParser.java:341)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientType(ElytronXmlParser.java:273)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:185)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:164)
> ...
> {code}
> It does not work even if dollar sign is escaped:
> {code}
> <crypt-password crypt="\$1\$somesalt\$W.KCTbPSiFDGffAGOjcBc."/>
> {code}
> Value of crypt was created in the same way as in UnixMD5CryptUtilTest [1].
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/371c1334fde7527d...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JGRP-2196) TP: internal thread pool is not shut down
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2196?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-2196.
----------------------------
Resolution: Done
> TP: internal thread pool is not shut down
> -----------------------------------------
>
> Key: JGRP-2196
> URL: https://issues.jboss.org/browse/JGRP-2196
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.4
>
>
> In {{TP.destroy()}}, the regular thread pool and timer are shut down, but not the internal thread pool. The result is that sometimes closing a channel takes a longer time (the max idle time for a thread in the pool). This only happens when an internal thread is active at the time of shut down.
> Also use a separate thread factory for internal threads, so we can see by the naming whether a thread is regular or internal, e.g. "jgroups-23" (regular) versus "jgroups-int-33"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1247) Elytron client configuration file throws ConfigXMLParseException when hashed-password is used
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-1247?page=com.atlassian.jira.plugin.s... ]
Pedro Igor commented on ELY-1247:
---------------------------------
Can we close this one as it seems to not be a issue anymore due to https://issues.jboss.org/browse/ELY-1252 ?
> Elytron client configuration file throws ConfigXMLParseException when hashed-password is used
> ---------------------------------------------------------------------------------------------
>
> Key: ELY-1247
> URL: https://issues.jboss.org/browse/ELY-1247
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
>
> When Elytron client configuration file includes {{configuration.authentication-client.authentication-configurations.configuration.credentials.hashed-password}} element then ConfigXMLParseException is thrown during parsing of configuration file.
> For following configuration file:
> {code}
> <configuration>
> <authentication-client xmlns="urn:elytron:1.0">
> <authentication-rules>
> <rule use-configuration="auth-config"/>
> </authentication-rules>
> <authentication-configurations>
> <configuration name="auth-config">
> <sasl-mechanism-selector selector="DIGEST-MD5"/>
> <set-user-name name="user"/>
> <credentials>
> <hashed-password algorithm="simple-digest-md5" hash="cGFzc3dvcmQ="/>
> </credentials>
> </configuration>
> </authentication-configurations>
> </authentication-client>
> </configuration>
> {code}
> following exception is thrown:
> {code}
> org.wildfly.client.config.ConfigXMLParseException: CONF0005: Unexpected element "authentication-client" in namespace "urn:elytron:1.0" encountered
> at vfs:/content/wildfly-config-xml.war/META-INF/wildfly-config.xml:15:5
> at org.wildfly.client.config.ConfigurationXMLStreamReader.unexpectedElement(ConfigurationXMLStreamReader.java:245)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:197)
> at org.wildfly.security.auth.client.ElytronXmlParser.parseAuthenticationClientConfiguration(ElytronXmlParser.java:146)
> at com.redhat.eap.qe.elytron.authnctx.WildflyConfigXmlServlet.parseAndCreateAuthenticationClientConfiguration(WildflyConfigXmlServlet.java:120)
> ... 41 more
> {code}
> When {{hashed-password}} is changed to {{clear-password}}:
> {code}
> <clear-password password="password"/>
> {code}
> then it is parsed correctly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1624) Map Handling with Property Reactive Always Enabled
by KimJohn Quinn (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1624?page=com.atlassian.jira.plugi... ]
KimJohn Quinn commented on DROOLS-1624:
---------------------------------------
Let me work on building out a test case similar to our problem.
Also, I learned something from this about using the KieHelper, thanks!
> Map Handling with Property Reactive Always Enabled
> --------------------------------------------------
>
> Key: DROOLS-1624
> URL: https://issues.jboss.org/browse/DROOLS-1624
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.0.0.Final
> Environment: * JDK8
> * Docker running Alpine
> Reporter: KimJohn Quinn
> Assignee: Mario Fusco
> Priority: Minor
>
> Referencing a conversation on [Google Groups - Drools Usage|https://groups.google.com/forum/?fromgroups#!topic/drools-usage/G7r...] and as requested by Mario Fusco...
> We currently have a ruleset that relies heavily on Map facts. In Drools 6.5 we fire approximately 400 rules.
> In Drools 7.0 we get only about 50 rules unless we add the "<property key="drools.propertySpecific" value="ALLOWED"/>" to the kmodule.xml, in which case we fire the full 400 rules or by using @Watch(*) or @Watch(!*) on the rules. It "seems" like only the first evaluations of the rules are firing and then no others after that.
> Our flow generally follows something like below, within a stateful session, using rules only. We fire all rules per-request then close the session.
> Watch for changes to the Map properties
> If a certain property or properties exist a 'populate' rule fires (calls modify())
> The populate rule enriches the map fact. (calls modify())
> Based on #3, more rules fire when certain properties exist (calls modify())
> We are work heavily with rules that depend on loaded available facts up-front and computed properties throughout evaluation.
> I have a couple of usage questions regarding Drools 7, the default enabling of Property Reactive and using Maps as the facts:
> In general, how do maps work with property reactive and respond to modify/insert events? Does Drools look at the Map as a whole, any change re-evaluates the tree, or each individual property within the map re-evaluates the change?
> In Drools 7, by defaulting the property reactive setting, does that mean all rules need to be annotated or they should they work as is (dao or map-based facts) when using modify/insert?
> For reference, we are relying on this doco https://docs.jboss.org/drools/release/7.0.0.Final/drools-docs/html_single....
> I am looking into details or an example how to properly use Maps in Drools 7 with Property Reactive features always enabled (as suggested per the doco)....
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1258) ElytronAuthenticator.getPasswordAuthentication() cannot obtain PasswordFactory for Elytron algorithms
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1258?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1258:
------------------------------
Description:
{{ElytronAuthenticator.getPasswordAuthentication()}} cannot obtain PasswordFactory for Elytron related algorithms. It is caused by missing WildFlyElytronProvider (since {{Security::getProviders}} is used for obtaining providers) for {{PasswordFactory.getInstance}} in [1].
It results to hidden NoSuchAlgorithmException with message _ELY08028: Invalid algorithm "clear"_ and stacktrace:
{code}
org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121)
org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:75)
org.wildfly.security.auth.util.ElytronAuthenticator.getPasswordAuthentication(ElytronAuthenticator.java:92)
java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
...
{code}
It causes that even if element {{net-authenticator}} from Elytron client configuration file correctly sets ElytronAuthenticator as default Authenticator, it is not able to work with Elytron related algorithms.
[1] https://github.com/wildfly-security/wildfly-elytron/blob/4df6f4726b7cf070...
was:
{{ElytronAuthenticator.getPasswordAuthentication()}} cannot obtain PasswordFactory for Elytron related algorithms. It is caused by missing WildFlyElytronProvider (since {{Security::getProviders}} is used for obtaining providers) for {{PasswordFactory.getInstance}} in [1].
It results to hidden NoSuchAlgorithmException with message _ELY08028: Invalid algorithm "clear"_ and stacktrace:
{code}
org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121)
org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:75)
org.wildfly.security.auth.util.ElytronAuthenticator.getPasswordAuthentication(ElytronAuthenticator.java:92)
java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
...
{code}
It causes that even if element {{net-authenticator}} from Elytron client configuration file correctly sets ElytronAuthenticator as default Authenticator, it is not able to work with Elytron related algorithms which means it breaks feature from RFE7-567 - Client Side Security (Elytron Client) => we request blocker flag.
[1] https://github.com/wildfly-security/wildfly-elytron/blob/4df6f4726b7cf070...
> ElytronAuthenticator.getPasswordAuthentication() cannot obtain PasswordFactory for Elytron algorithms
> -----------------------------------------------------------------------------------------------------
>
> Key: ELY-1258
> URL: https://issues.jboss.org/browse/ELY-1258
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta52
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> {{ElytronAuthenticator.getPasswordAuthentication()}} cannot obtain PasswordFactory for Elytron related algorithms. It is caused by missing WildFlyElytronProvider (since {{Security::getProviders}} is used for obtaining providers) for {{PasswordFactory.getInstance}} in [1].
> It results to hidden NoSuchAlgorithmException with message _ELY08028: Invalid algorithm "clear"_ and stacktrace:
> {code}
> org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:121)
> org.wildfly.security.password.PasswordFactory.getInstance(PasswordFactory.java:75)
> org.wildfly.security.auth.util.ElytronAuthenticator.getPasswordAuthentication(ElytronAuthenticator.java:92)
> java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> ...
> {code}
> It causes that even if element {{net-authenticator}} from Elytron client configuration file correctly sets ElytronAuthenticator as default Authenticator, it is not able to work with Elytron related algorithms.
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/4df6f4726b7cf070...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years