[JBoss JIRA] (WFLY-7278) Unable to load LdapCtxFactory from elytron module
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7278?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7278:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> Unable to load LdapCtxFactory from elytron module
> -------------------------------------------------
>
> Key: WFLY-7278
> URL: https://issues.jboss.org/browse/WFLY-7278
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Fix For: 11.0.0.Alpha1
>
>
> When *ldap-key-store* is used in *trust-manager*, trust-manager creation fails:
> {code:java}
> Caused by: javax.naming.NamingException: WFLYNAM0027: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.wildfly.extension.elytron:main" from local module loader @77a57272 (finder: local module finder @7181ae3f (roots: /home/jkalina/wildfly/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/home/jkalina/wildfly/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory from [Module "org.wildfly.extension.elytron:main" from local module loader @77a57272 (finder: local module finder @7181ae3f (roots: /home/jkalina/wildfly/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/home/jkalina/wildfly/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:118)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:99)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89)
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43)
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
> at javax.naming.InitialContext.init(InitialContext.java:244)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
> at org.wildfly.security.auth.realm.ldap.SimpleDirContextFactoryBuilder$SimpleDirContextFactory.createDirContext(SimpleDirContextFactoryBuilder.java:286)
> at org.wildfly.security.auth.realm.ldap.SimpleDirContextFactoryBuilder$SimpleDirContextFactory.obtainDirContext(SimpleDirContextFactoryBuilder.java:222)
> at org.wildfly.extension.elytron.DirContextDefinition.lambda$null$0(DirContextDefinition.java:148)
> at org.wildfly.security.keystore.LdapKeyStoreSpi.obtainDirContext(LdapKeyStoreSpi.java:120)
> ... 16 more
> java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory from [Module "org.wildfly.extension.elytron:main" from local module loader @77a57272 (finder: local module finder @7181ae3f (roots: /home/jkalina/wildfly/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules,/home/jkalina/wildfly/wildfly/build/target/wildfly-11.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:199)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:364)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:352)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:94)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:113)
> ... 28 more
> {code}
> Direct key-store aliases listing using works ok:
> {code:java}
> /subsystem=elytron/ldap-key-store=LKS1/:read-children-names(child-type=alias)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7271) Review elytron jdbc-realm resource XSD definition
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7271?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse updated WFLY-7271:
-----------------------------------
Fix Version/s: 11.0.0.Alpha1
> Review elytron jdbc-realm resource XSD definition
> -------------------------------------------------
>
> Key: WFLY-7271
> URL: https://issues.jboss.org/browse/WFLY-7271
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
> Fix For: 11.0.0.Alpha1
>
>
> * Wouldn't {{xsd:all}} be more proper than {{xsd:sequence}} here, as it doesn't required elements in exact order.
> * In XSD attribute-mapping attribute {{to}} is declared as optional, but in fact it is required.
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/jdbc-realm=a:add(principal-query=[{sql="a",data-source="ExampleDS",attribute-mapping=[{index=0}]}])
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0155: to may not be null",
> "rolled-back" => true
> }
> {code}
> * simple-digest-mapper, salted-simple-digest-mapper and scram-mapper missing {{algorithm}} attribute in XSD
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7313) Impossible to use environment variables or system properties in permissions.xml
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-7313?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-7313:
-------------------------------
Priority: Major (was: Blocker)
> Impossible to use environment variables or system properties in permissions.xml
> -------------------------------------------------------------------------------
>
> Key: WFLY-7313
> URL: https://issues.jboss.org/browse/WFLY-7313
> Project: WildFly
> Issue Type: Feature Request
> Affects Versions: 10.1.0.Final
> Reporter: Adrian Boangiu
> Assignee: Jason Greene
>
> Without this feature it is impossible to migrate "variable" Java file permissions such as:
> permission java.io.FilePermission "${java.io.tmpdir}","read";
> permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete";
> permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete";
> that were defined in Java policy file in previous verions of JBoss.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7313) Impossible to use environment variables or system properties in permissions.xml
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-7313?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-7313:
-------------------------------
Fix Version/s: (was: 10.1.0.Final)
(was: 10.2.0.Final)
> Impossible to use environment variables or system properties in permissions.xml
> -------------------------------------------------------------------------------
>
> Key: WFLY-7313
> URL: https://issues.jboss.org/browse/WFLY-7313
> Project: WildFly
> Issue Type: Feature Request
> Affects Versions: 10.1.0.Final
> Reporter: Adrian Boangiu
> Assignee: Jason Greene
>
> Without this feature it is impossible to migrate "variable" Java file permissions such as:
> permission java.io.FilePermission "${java.io.tmpdir}","read";
> permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete";
> permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete";
> that were defined in Java policy file in previous verions of JBoss.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7313) Impossible to use environment variables or system properties in permissions.xml
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-7313?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-7313:
-------------------------------
Component/s: EE
> Impossible to use environment variables or system properties in permissions.xml
> -------------------------------------------------------------------------------
>
> Key: WFLY-7313
> URL: https://issues.jboss.org/browse/WFLY-7313
> Project: WildFly
> Issue Type: Feature Request
> Components: EE
> Affects Versions: 10.1.0.Final
> Reporter: Adrian Boangiu
> Assignee: Jason Greene
>
> Without this feature it is impossible to migrate "variable" Java file permissions such as:
> permission java.io.FilePermission "${java.io.tmpdir}","read";
> permission java.io.FilePermission "${jboss.home.dir}${/}bin${/}javamelody${/}-","read,write,delete";
> permission java.io.FilePermission "${app.home.dir}${/}log${/}-","read,write,delete";
> that were defined in Java policy file in previous verions of JBoss.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7316) LDAP referrals does not work for Elytron dir-context since value of dir-context.referral-mode is always ignored
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7316?page=com.atlassian.jira.plugin.... ]
Jan Kalina edited comment on WFLY-7316 at 10/14/16 9:26 AM:
------------------------------------------------------------
By discussion, maybe there will be need to add "filter" attribute to the ldap-realm, similar like in ldap-key-store already is to work with referrals:
{code:java}
(|(objectClass=refferal)(uid={0}))
{code}
(will have to check yet if it helps, but by Ondřej it is solved in Picketbox by this way)
was (Author: honza889):
By discussion, maybe there will be need to add "filter" attribute to the ldap-realm, similar like in ldap-key-store already is to work with referrals:
(|(objectClass=refferal)(uid={0}))
(will have to check yet if it helps, but by Ondřej it is solved in Picketbox by this way)
> LDAP referrals does not work for Elytron dir-context since value of dir-context.referral-mode is always ignored
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7316
> URL: https://issues.jboss.org/browse/WFLY-7316
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Blocker
>
> Elytron dir-context is not able to follow/throw referrals in LDAP search. Value set in Elytron {{dir-context.referral-mode}} is ignored by Elytron.
> InitialLdapContext {{java.naming.referral}} parameter is internally always set to value {{ignore}}. It is caused by ignoring {{ReferralMode}} parameter in {{obtainDirContext}} of {{org.wildfly.security.auth.realm.ldap.SimpleDirContextFactoryBuilder$SimpleDirContextFactory}} [1].
> We request blocker flag since this issue causes that referrals cannot be used for LDAP search with Elytron.
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (WFLY-7316) LDAP referrals does not work for Elytron dir-context since value of dir-context.referral-mode is always ignored
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7316?page=com.atlassian.jira.plugin.... ]
Jan Kalina commented on WFLY-7316:
----------------------------------
By discussion, maybe there will be need to add "filter" attribute to the ldap-realm, similar like in ldap-key-store already is to work with referrals:
(|(objectClass=refferal)(uid={0}))
(will have to check yet if it helps, but by Ondřej it is solved in Picketbox by this way)
> LDAP referrals does not work for Elytron dir-context since value of dir-context.referral-mode is always ignored
> ---------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7316
> URL: https://issues.jboss.org/browse/WFLY-7316
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Blocker
>
> Elytron dir-context is not able to follow/throw referrals in LDAP search. Value set in Elytron {{dir-context.referral-mode}} is ignored by Elytron.
> InitialLdapContext {{java.naming.referral}} parameter is internally always set to value {{ignore}}. It is caused by ignoring {{ReferralMode}} parameter in {{obtainDirContext}} of {{org.wildfly.security.auth.realm.ldap.SimpleDirContextFactoryBuilder$SimpleDirContextFactory}} [1].
> We request blocker flag since this issue causes that referrals cannot be used for LDAP search with Elytron.
> [1] https://github.com/wildfly-security/wildfly-elytron/blob/cb57f2f0ffcdb147...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (DROOLS-1323) DefaultAgenda.immediateHalt takes up 20% of performance in statefull cases: investigate why
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1323?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1323:
-------------------------------------
Attachment: Selection_249.png
but a big dataset benchmark doesn't confirm: no gain (loss even)...
[^Selection_249.png]
> DefaultAgenda.immediateHalt takes up 20% of performance in statefull cases: investigate why
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-1323
> URL: https://issues.jboss.org/browse/DROOLS-1323
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Attachments: Selection_240.png, Selection_241.png, Selection_245.png, Selection_246.png, Selection_247.png, Selection_249.png
>
>
> Mario and Geoffrey will investigate, but here's the profiler reports to prove it.
> to reproduce: OptaPlannerExamplesApp -> cloud balancing use case -> load dataset with 1600computer + turn off refresh checkbox -> start cpu profiling -> button solve
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months