January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7845) Connection pool in Elytron dir-context is not configurable

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7845?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7845: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Connection pool in Elytron dir-context is not configurable > ---------------------------------------------------------- > > Key: WFLY-7845 > URL: https://issues.jboss.org/browse/WFLY-7845 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > Elytron dir-context resource allows to configure connection pool through its {{enable-connection-pooling}} attribute. However another options for connection pool is not able to be set in application server configuration. It means that connection pool can be used but cannot be parametrized. See [1] for another Java connection pool options. > [1] http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7844) Elytron dir-context supports only plaintext password

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7844?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7844: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Elytron dir-context supports only plaintext password > ---------------------------------------------------- > > Key: WFLY-7844 > URL: https://issues.jboss.org/browse/WFLY-7844 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > > Only plaintext password is currently able to be configured in Elytron dir-context resource. Any integration with Credential store is missing. > We request blocker since it seems that there is currently no option how to provide non-plaintext password for dir-context to server configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7843) Initial context factory is not able to be set in Elytron dir-context

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7843?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7843: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Initial context factory is not able to be set in Elytron dir-context > -------------------------------------------------------------------- > > Key: WFLY-7843 > URL: https://issues.jboss.org/browse/WFLY-7843 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > Elytron subsystem does not allow to configure custom Initial context factory for dir-context. > Elytron {{org.wildfly.security.auth.realm.ldapSimpleDirContextFactoryBuilder}} includes setter for field {{initialContextFactory}}, but integration for Elytron subsystem is missing. This means that default value {{com.sun.jndi.ldap.LdapCtxFactory}} is always used by Application server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7844) Elytron dir-context supports only plaintext password

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7844: ---------------------------------- Summary: Elytron dir-context supports only plaintext password Key: WFLY-7844 URL: https://issues.jboss.org/browse/WFLY-7844 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Blocker Only plaintext password is currently able to be configured in Elytron dir-context resource. Any integration with Credential store is missing. We request blocker since it seems that there is currently no option how to provide non-plaintext password for dir-context to server configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7843) Initial context factory is not able to be set in Elytron dir-context

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7843: ---------------------------------- Summary: Initial context factory is not able to be set in Elytron dir-context Key: WFLY-7843 URL: https://issues.jboss.org/browse/WFLY-7843 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical Elytron subsystem does not allow to configure custom Initial context factory for dir-context. Elytron {{org.wildfly.security.auth.realm.ldapSimpleDirContextFactoryBuilder}} includes setter for field {{initialContextFactory}}, but integration for Elytron subsystem is missing. This means that default value {{com.sun.jndi.ldap.LdapCtxFactory}} is always used by Application server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tibor Digana commented on WFLY-7841: ------------------------------------ Yes, I will extract the code. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7842) Security-Realm Authorization over LDAP doesn't permit multiple Attribute names as filter.

by Daniel Draper (JIRA)

Daniel Draper created WFLY-7842: ----------------------------------- Summary: Security-Realm Authorization over LDAP doesn't permit multiple Attribute names as filter. Key: WFLY-7842 URL: https://issues.jboss.org/browse/WFLY-7842 Project: WildFly Issue Type: Bug Environment: CentOS release 6.8 (Final) JBoss Admin Command-line Interface JBOSS_HOME: /opt/wildfly/10.1.0 JBoss AS release: 2.2.0.Final "Kenny" JBoss AS product: WildFly Full 10.1.0.Final JAVA_HOME: null java.version: 1.8.0_40 java.vm.vendor: Oracle Corporation java.vm.version: 25.40-b25 os.name: Linux os.version: 4.6.3-1.el6.elrepo.x86_64 Reporter: Daniel Draper Assignee: Jason Greene When hooking up our Wildfly Application to our SSO (CAS) for authentication and delegating Authorization to a Security Realm and then using LDAP we ran into the following problem: *Use Case* We want to use authorization inside a Security-Realm through LDAP. In our LDAP setup we have a Group-To-Principal matching of the form "_member=uid=x" OR "submember=uid=x_" depending on if the user was added manually or through an autodomain. Unfortunately as far as we could tell using two attributes in the Polish Notation (as is required by [LDAP|https://ldapwiki.com/wiki/LDAP%20filters%20Syntax%20and%20Choices]) seems to be impossible for the wildfly configuration. We tried the following in the standalone-accounting.xml (in different iterations and ways to place the parenthesis) which all lead to an 'unbalanced Parenthesis' or similar error when starting up wildfly. {code:xml} <management> <security-realms> <security-realm name="bla"> <authorization> <ldap connection="ldap"> <username-to-dn> <username-is-dn/> </username-to-dn> <group-search group-name="SIMPLE" iterative="false" group-dn-attribute="cn" group-name-attribute="cn"> <group-to-principal search-by="SIMPLE" base-dn="ou=roles,***" recursive="false"> <membership-filter principal-attribute="|(submember=uid={0})(member=uid={0})"/> </group-to-principal> </group-search> </ldap> </authorization> </security-realm> </security-realms> </management> {code} We then found the filterString is parsed the following way: (See [LdapGroupSearcherFactory#L115|https://github.com/wildfly/wildfly-core/blo...]) {code:java} this.filterString = String.format("(%s={0})", principalAttribute); {code} which seems to make multiple attribute names as a filter impossible, which makes our use case as above impossible. Asked in [Forums|https://developer.jboss.org/thread/273435], but since I didn't get any answers for 3 weeks opening here. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tomas Remes commented on WFLY-7841: ----------------------------------- [~tibor17] Can you please provide simple reproducer and exception stacktrace? > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-7841: ------------------------------- Description: The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : * _@ApplicationScoped_ job instance was passed to executor from caller. * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. was: The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService_. The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : * _@ApplicationScoped_ job instance was passed to executor from caller. * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance It looks to me that javax.enterprise.concurrent has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService#scheduleAtFixedRate()_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance and then I called _scheduleAtFixedRate(job, 5, 60, SECONDS)_ > It looks to me that _javax.enterprise.concurrent_ has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7841) ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context.

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-7841?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-7841: ------------------------------- Description: The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService_. The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : * _@ApplicationScoped_ job instance was passed to executor from caller. * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance It looks to me that javax.enterprise.concurrent has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. was: The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService_. The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : * _@ApplicationScoped_ job instance was passed to executor from caller. * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ It looks to me that javax.enterprise.concurrent has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. > ManagedScheduledExecutorService could not find EntityManager produced by CDI producer. No active context. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7841 > URL: https://issues.jboss.org/browse/WFLY-7841 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 10.0.0.Final > Reporter: Tibor Digana > Assignee: Stuart Douglas > > The problem is that _EntityManager_ does not have managed delegate within a job executed by _ManagedScheduledExecutorService_. > The _EntityManager_ is produced by CDI producer and entire web application is able to work with injected _EntityManager_ except for the jobs. > I tried to schedule executing the job in two ways and both finished with same issue (No managed context in _EntityManager_) : > * _@ApplicationScoped_ job instance was passed to executor from caller. > * The job was changed to _RequestScoped_ and _ContextProxy#createContextualProxy()_ created the Job bean instance > It looks to me that javax.enterprise.concurrent has a different _BeanManager_ and therefore has no notion about my CDI Producer of _EntityManager_. The producer is regular producer of _EntityManager_ in JavaEE. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 January 2017