[JBoss JIRA] (DROOLS-1616) Revise coverage of DMN input tests
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-1616:
-------------------------------------
Summary: Revise coverage of DMN input tests
Key: DROOLS-1616
URL: https://issues.jboss.org/browse/DROOLS-1616
Project: Drools
Issue Type: Task
Components: dmn engine
Affects Versions: 7.0.0.Final
Reporter: Tibor Zimányi
Assignee: Tibor Zimányi
Priority: Minor
Fix For: 7.1.0.Final
Input tests revision. I will provide PR for this.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JGRP-2172) Non-blocking flow control
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2172:
--------------------------------
A minor change in semantics wrt non-blocking flow control versus blocking flow control: if sender P sends messages 1 (700K) and 2 (300K), then blocking flow control guarantees that P1 is sent first down the stack into UNICAST3 land where it gets a seqno, then P2. Thus, P1 will be delivered before P2.
However, these semantics are not guaranteed with non-blocking flow control: if we for example have 500K left, then P1 (700K) will be queued and the call returns so that P can send message 2. P2 (300K) will be sent successfully, but P1 will only get sent once we get new credits from the destination member. This means P2 may get delivered before P1.
Typically this is not a problem as P1 and P2 are probably unrelated, or else P would wait for a response to P1 before sending P2 (e.g. a GET request, then a GET response and - based on the response - a PUT request).
Just wanted to point this out.
> Non-blocking flow control
> -------------------------
>
> Key: JGRP-2172
> URL: https://issues.jboss.org/browse/JGRP-2172
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 4.0.4
>
>
> Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
> Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded). The max queue size is given in bytes, so we can estimate what the memory penalty for reaching that size would be (if bounded).
> The queued messages are sent when credits arrive. TBD: when credits arrive, should blocked threads or queued messages be released first?
> Non-blocking flow control can be used by both external and internal threads.
> If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1247) Elytron client configuration file throws ConfigXMLParseException when hashed-password is used
by Ondrej Lukas (JIRA)
Ondrej Lukas created ELY-1247:
---------------------------------
Summary: 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
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
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.
We request blocker flag since using hashed password is not possible in Elytron client configuration file which breaks feature in RFE EAP7-567 Client Side Security (Elytron Client).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ELY-1247) Elytron client configuration file throws ConfigXMLParseException when hashed-password is used
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1247?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1247:
------------------------------
Description:
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.
was:
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.
We request blocker flag since using hashed password is not possible in Elytron client configuration file which breaks feature in RFE EAP7-567 Client Side Security (Elytron Client).
> 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: Darran Lofthouse
> 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)
8 years, 10 months
[JBoss JIRA] (ELY-1247) Elytron client configuration file throws ConfigXMLParseException when hashed-password is used
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/ELY-1247?page=com.atlassian.jira.plugin.s... ]
Ondrej Lukas updated ELY-1247:
------------------------------
Affects Version/s: 1.1.0.Beta52
> 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: Darran Lofthouse
> 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)
8 years, 10 months
[JBoss JIRA] (WFLY-8948) SAML2STSLoginModule cannot be configured with module options instead of configFile
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFLY-8948?page=com.atlassian.jira.plugin.... ]
Jiri Ondrusek updated WFLY-8948:
--------------------------------
Description:
It is not possible to configure the SAML2STSLoginModule by using module options instead of configFile:
<security-domain name="sts" cache-type="default">
<authentication>
<login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule" flag="required" module="org.picketlink">
<module-option name="serviceName" value="PicketLinkSTS"/>
<module-option name="portName" value="PicketLinkSTSPort"/>
<module-option name="endpointAddress" value="http://localhost:8080/picketlink-sts/PicketLinkSTS"/>
<module-option name="username" value="admin"/>
<module-option name="password" value="admin"/>
See BZ for more information.
was:
It is not possible to configure the SAML2STSLoginModule by using module options instead of configFile:
<security-domain name="sts" cache-type="default">
<authentication>
<login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule" flag="required" module="org.picketlink">
<module-option name="serviceName" value="PicketLinkSTS"/>
<module-option name="portName" value="PicketLinkSTSPort"/>
<module-option name="endpointAddress" value="http://localhost:8080/picketlink-sts/PicketLinkSTS"/>
<module-option name="username" value="admin"/>
<module-option name="password" value="admin"/>
> SAML2STSLoginModule cannot be configured with module options instead of configFile
> ----------------------------------------------------------------------------------
>
> Key: WFLY-8948
> URL: https://issues.jboss.org/browse/WFLY-8948
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Security
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
>
> It is not possible to configure the SAML2STSLoginModule by using module options instead of configFile:
> <security-domain name="sts" cache-type="default">
> <authentication>
> <login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule" flag="required" module="org.picketlink">
> <module-option name="serviceName" value="PicketLinkSTS"/>
> <module-option name="portName" value="PicketLinkSTSPort"/>
> <module-option name="endpointAddress" value="http://localhost:8080/picketlink-sts/PicketLinkSTS"/>
> <module-option name="username" value="admin"/>
> <module-option name="password" value="admin"/>
> See BZ for more information.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-8948) SAML2STSLoginModule cannot be configured with module options instead of configFile
by Jiri Ondrusek (JIRA)
Jiri Ondrusek created WFLY-8948:
-----------------------------------
Summary: SAML2STSLoginModule cannot be configured with module options instead of configFile
Key: WFLY-8948
URL: https://issues.jboss.org/browse/WFLY-8948
Project: WildFly
Issue Type: Bug
Components: EJB, Security
Reporter: Jiri Ondrusek
Assignee: Jiri Ondrusek
It is not possible to configure the SAML2STSLoginModule by using module options instead of configFile:
<security-domain name="sts" cache-type="default">
<authentication>
<login-module code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule" flag="required" module="org.picketlink">
<module-option name="serviceName" value="PicketLinkSTS"/>
<module-option name="portName" value="PicketLinkSTSPort"/>
<module-option name="endpointAddress" value="http://localhost:8080/picketlink-sts/PicketLinkSTS"/>
<module-option name="username" value="admin"/>
<module-option name="password" value="admin"/>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months