[JBoss JIRA] (DROOLS-1416) DRL Dumper Not Printing the content of ConditionalBranch
by Siyad Theyparambil Mohammed (JIRA)
Siyad Theyparambil Mohammed created DROOLS-1416:
---------------------------------------------------
Summary: DRL Dumper Not Printing the content of ConditionalBranch
Key: DROOLS-1416
URL: https://issues.jboss.org/browse/DROOLS-1416
Project: Drools
Issue Type: Bug
Components: tools
Affects Versions: 6.4.0.Final
Reporter: Siyad Theyparambil Mohammed
Assignee: Mario Fusco
Priority: Blocker
While trying to use conditionalbranch api for handling multiple if-then blocks, the DRL dumper is not printing the content we have used for conditionalbranch. Please find the sample code below and the restuls
*+Code+*
PackageDescr pkg = DescrFactory.newPackage()
.name( "org.drools.compiler" )
.newRule().name( "test" )
.lhs()
.pattern("Cheese").constraint( "type == \"stilton\"" ).end()
.conditionalBranch()
.condition().constraint("price < 10").end()
.consequence().name("c1").end()
.end()
.pattern("Cheese").constraint( "type == \"cheddar\"" ).end()
.conditionalBranch()
.condition().constraint("price > 10").end()
.consequence().name("c2").end()
.end()
.end()
.rhs( "// do something" )
.namedRhs( "c1", "// do something else\n" )
.end()
.getDescr();
return new DrlDumper().dump( pkg );
*+Output+*
package org.drools.compiler
rule "test"
when
Cheese( type == "stilton" )
Cheese( type == "cheddar" )
then
// do something
then[c1]
// do something else
end
In the above example the content "price < 10" and "price > 10" which we have used for conditionalBranch is not getting printed. On further investigation we found the drl.mvel template does not have the import org.drools.compiler.lang.descr.ConditionalBranchDescr.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7158) Working with multiple keys in key store
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7158?page=com.atlassian.jira.plugin.... ]
Martin Choma edited comment on WFLY-7158 at 1/19/17 11:02 AM:
--------------------------------------------------------------
As I understand {code}<credential-reference store="test" alias="the-key-alias"/>{code} "returns" string stored under alias the-key-alias in credential store test. I still don't get how should that solve the issue. What am I missing?
Using your example issue is if {{key-store="LocalhostKeystore"}} contains 2 private keys. Then we need way how to specify right key password on key-manager resource.
was (Author: mchoma):
As I understand {code}<credential-reference store="test" alias="the-key-alias"/>{code} "returns" string stored under alias the-key-alias in credential store test. I still don't get how should that solve the issue. What am I missing?
Using your example issue is if {{key-store="LocalhostKeystore"}} contains 2 private keys. Then we need way how to specify right key password.
> Working with multiple keys in key store
> ---------------------------------------
>
> Key: WFLY-7158
> URL: https://issues.jboss.org/browse/WFLY-7158
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> In case when 2 keys are present in keystore, then alias-filter (filtering into single key) on key-store resource has to be specified, otherwise key-manager can't be created. If user want to use keystore with multiple keys, user has to configure multiple key-store elements with specified alias-filter (filtering into single key).
> That is pretty inconvinient. Probably introducing *alias attribute on key-manager* would be more intuitive solution to this situation.
> {code}
> /subsystem=elytron/key-managers=server:add(key-store=server,algorithm="SunX509",password=key-password)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7158) Working with multiple keys in key store
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/WFLY-7158?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFLY-7158:
------------------------------------
As I understand {code}<credential-reference store="test" alias="the-key-alias"/>{code} "returns" string stored under alias the-key-alias in credential store test. I still don't get how should that solve the issue. What am I missing?
Using your example issue is if {{key-store="LocalhostKeystore"}} contains 2 private keys. Then we need way how to specify right key password.
> Working with multiple keys in key store
> ---------------------------------------
>
> Key: WFLY-7158
> URL: https://issues.jboss.org/browse/WFLY-7158
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> In case when 2 keys are present in keystore, then alias-filter (filtering into single key) on key-store resource has to be specified, otherwise key-manager can't be created. If user want to use keystore with multiple keys, user has to configure multiple key-store elements with specified alias-filter (filtering into single key).
> That is pretty inconvinient. Probably introducing *alias attribute on key-manager* would be more intuitive solution to this situation.
> {code}
> /subsystem=elytron/key-managers=server:add(key-store=server,algorithm="SunX509",password=key-password)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (ELY-672) Getting identity by DN in Elytron ldap-realm should be case insensitive
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-672?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina updated ELY-672:
---------------------------
Fix Version/s: 1.1.0.Beta12
> Getting identity by DN in Elytron ldap-realm should be case insensitive
> -----------------------------------------------------------------------
>
> Key: ELY-672
> URL: https://issues.jboss.org/browse/ELY-672
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Realms
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Fix For: 1.1.0.Beta12
>
>
> Elytron ldap-realm allows to use DN as username (e.g. full {{uid=jduke,ou=People,dc=jboss,dc=org}} can be used instead of {{jduke}}). However implementation requires that used DN must start with rdn-identifier in the same case sensitivity as is used in server configuration. Otherwise authentication fails. It means when server configuration uses {{rdn-identifier=uid}} then only {{uid=jduke,...}} can be correctly used, {{UID=jduke,...}} will fail.
> LDAP specification does not talk about case sensitivity of attributes, but most of LDAP servers work with attributes as case insensitive.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7158) Working with multiple keys in key store
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7158?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7158 at 1/19/17 10:44 AM:
------------------------------------------------------------
The attribute *alias-filter* was not added in the end.
[~pskopek] has added this feature (specifying which alias from keystore to use) as *credential-reference* (attribute *alias*) instead.
See https://github.com/wildfly-security/elytron-subsystem/blob/master/src/tes...
was (Author: honza889):
The attribute *alias-filter* was not added in the end.
@pskopek has added this feature (specifying which alias from keystore to use) as *credential-reference* (attribute *alias*) instead.
See https://github.com/wildfly-security/elytron-subsystem/blob/master/src/tes...
> Working with multiple keys in key store
> ---------------------------------------
>
> Key: WFLY-7158
> URL: https://issues.jboss.org/browse/WFLY-7158
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> In case when 2 keys are present in keystore, then alias-filter (filtering into single key) on key-store resource has to be specified, otherwise key-manager can't be created. If user want to use keystore with multiple keys, user has to configure multiple key-store elements with specified alias-filter (filtering into single key).
> That is pretty inconvinient. Probably introducing *alias attribute on key-manager* would be more intuitive solution to this situation.
> {code}
> /subsystem=elytron/key-managers=server:add(key-store=server,algorithm="SunX509",password=key-password)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFLY-7158) Working with multiple keys in key store
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7158?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7158:
----------------------------------
The attribute *alias-filter* was not added in the end.
@pskopek has added this feature (specifying which alias from keystore to use) as *credential-reference* (attribute *alias*) instead.
See https://github.com/wildfly-security/elytron-subsystem/blob/master/src/tes...
> Working with multiple keys in key store
> ---------------------------------------
>
> Key: WFLY-7158
> URL: https://issues.jboss.org/browse/WFLY-7158
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 11.0.0.Alpha1
>
>
> In case when 2 keys are present in keystore, then alias-filter (filtering into single key) on key-store resource has to be specified, otherwise key-manager can't be created. If user want to use keystore with multiple keys, user has to configure multiple key-store elements with specified alias-filter (filtering into single key).
> That is pretty inconvinient. Probably introducing *alias attribute on key-manager* would be more intuitive solution to this situation.
> {code}
> /subsystem=elytron/key-managers=server:add(key-store=server,algorithm="SunX509",password=key-password)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (ELY-671) Usernames started with rdn-identifier works incorrectly in Elytron ldap-realm
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-671?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina updated ELY-671:
---------------------------
Fix Version/s: 1.1.0.Beta12
> Usernames started with rdn-identifier works incorrectly in Elytron ldap-realm
> -----------------------------------------------------------------------------
>
> Key: ELY-671
> URL: https://issues.jboss.org/browse/ELY-671
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Realms
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Critical
> Fix For: 1.1.0.Beta12
>
>
> In case username passed to {{org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity}} starts with the same string as is used in {{identityMapping.rdnIdentifier}} then authentication fails. It is caused by wrong condition in [1].
> Thrown exception in server log:
> {code}
> ERROR [io.undertow.request] (default task-12) UT005023: Exception handling request to /print-roles/protected/printRoles: java.lang.RuntimeException: ELY01078: Ldap-backed realm failed to obtain identity "uidyllic" from server
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.getIdentity(LdapSecurityRealm.java:625)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.exists(LdapSecurityRealm.java:545)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.verifyEvidence(LdapSecurityRealm.java:513)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1634)
> at org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:654)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:818)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:752)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:850)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:703)
> at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$SecurityIdentityCallbackHandler.handle(SecurityIdentityServerMechanismFactory.java:113)
> at org.wildfly.security.http.impl.UsernamePasswordAuthenticationMechanism.authenticate(UsernamePasswordAuthenticationMechanism.java:69)
> at org.wildfly.security.http.impl.BasicAuthenticationMechanism.evaluateRequest(BasicAuthenticationMechanism.java:151)
> at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:115)
> at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77)
> at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:106)
> at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:90)
> at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:74)
> at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:82)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
> at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1671)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1671)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1671)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1671)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:810)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.naming.InvalidNameException: Invalid name: uidyllic
> at javax.naming.ldap.Rfc2253Parser.doParse(Rfc2253Parser.java:111)
> at javax.naming.ldap.Rfc2253Parser.parseDn(Rfc2253Parser.java:70)
> at javax.naming.ldap.LdapName.parse(LdapName.java:785)
> at javax.naming.ldap.LdapName.<init>(LdapName.java:123)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.getIdentity(LdapSecurityRealm.java:571)
> ... 45 more
> {code}
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months