[JBoss JIRA] (ELY-760) Elytron Ldap Realm searches roles before validating password
by Ondrej Lukas (JIRA)
Ondrej Lukas created ELY-760:
--------------------------------
Summary: Elytron Ldap Realm searches roles before validating password
Key: ELY-760
URL: https://issues.jboss.org/browse/ELY-760
Project: WildFly Elytron
Issue Type: Bug
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
In Ldap Realm roles are searched before actual user password is validated. Ldap Realm uses following flow:
# searching for username
# searching for roles (i.e. searching for attributes)
# validating password for username
It means even if wrong password is used then roles in LDAP are searched. Password should be validated before some roles are searched. Current behavior can result to performance issues.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 7 months
[JBoss JIRA] (WFLY-7611) "Add a user to the master domain controller" format as title of paragraph and add dot at the end.
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-7611:
----------------------------------
Summary: "Add a user to the master domain controller" format as title of paragraph and add dot at the end.
Key: WFLY-7611
URL: https://issues.jboss.org/browse/WFLY-7611
Project: WildFly
Issue Type: Bug
Components: Documentation
Reporter: Hynek Švábek
Book: How to Configure Server Security
Revision: 8269434
Section: 3.1. Configure Password Authentication Between Slaves and the Domain Controller
Issue description:
There is missing dot "Add a user to the master domain controller"
This sentence should be title of paragraph.
Suggestions for improvement:
Correct form is "Add a user to the master domain controller." and make from this sentence title of paragraph.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 7 months
[JBoss JIRA] (WFLY-7610) Missing default value of filter-name in Elytron ldap-realm in CLI
by Ondrej Lukas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7610?page=com.atlassian.jira.plugin.... ]
Ondrej Lukas updated WFLY-7610:
-------------------------------
Description: Elytron {{ldap-realm.identity-mapping.filter-name}} attribute has not assigned default value in CLI. However according to XSD it has default value (rdn-identifier={0}). (was: Elytron {{ldap-realm.identity-mapping.filter-name}} attribute has not assigned default value in CLI. However according to XSD it has default value {{(rdn-identifier={0})}}.)
> Missing default value of filter-name in Elytron ldap-realm in CLI
> -----------------------------------------------------------------
>
> Key: WFLY-7610
> URL: https://issues.jboss.org/browse/WFLY-7610
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Labels: user_experience
>
> Elytron {{ldap-realm.identity-mapping.filter-name}} attribute has not assigned default value in CLI. However according to XSD it has default value (rdn-identifier={0}).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 7 months
[JBoss JIRA] (WFCORE-1934) Make number of thread size for ServerService Thread Pool configurable
by Masafumi Miura (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1934?page=com.atlassian.jira.plugi... ]
Masafumi Miura updated WFCORE-1934:
-----------------------------------
Issue Type: Enhancement (was: Bug)
> Make number of thread size for ServerService Thread Pool configurable
> ---------------------------------------------------------------------
>
> Key: WFCORE-1934
> URL: https://issues.jboss.org/browse/WFCORE-1934
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 2.2.0.Final
> Reporter: Masafumi Miura
> Assignee: Jason Greene
> Attachments: ServerServiceThreadPool_ejb_startup_singleton.zip, ServerServiceThreadPool_persistence_unit.zip
>
>
> Provide a way to configure {{maximumPoolSize}} of {{ServerService Thread Pool}}. It defaults to {{Integer.MAX_VALUE}} and it's unable to be changed in the current implementation:
>
> {quote}
> https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/...
> {code}
> 446 public synchronized void start(StartContext context) throws StartException {
> 447 executorService = new ThreadPoolExecutor(0, Integer.MAX_VALUE, 20L, TimeUnit.SECONDS,
> 448 new SynchronousQueue<Runnable>(), threadFactory);
> 449 }
> {code}
> {quote}
> Though the threads will disappear after 20 seconds of finishing a task, ulimit ({{nproc}}, max user processes) has a possibility to run out and "java.lang.OutOfMemoryError: unable to create new native thread" would occur depending on deployed applications. For example, an application coming with many {{<persistence-unit>}} entries in {{persistence.xml}} or a lot of @Startup @Singleton EJB can cause spawning a lot of {{ServerService Thread Pool}} thread.
> Even if ulimit can be configurable and it is recommended to be tuned in a production environment, making {{maximumPoolSize}} of {{ServerService Thread Pool}} configurable would be helpful.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 7 months
[JBoss JIRA] (WFLY-7609) There is an extra dot in front of sentence ".CLI Command for Using a New Security Realm"
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-7609:
----------------------------------
Summary: There is an extra dot in front of sentence ".CLI Command for Using a New Security Realm"
Key: WFLY-7609
URL: https://issues.jboss.org/browse/WFLY-7609
Project: WildFly
Issue Type: Bug
Components: Documentation
Reporter: Hynek Švábek
Book: How to Configure Server Security
Revision: 8269434
Section: 2.2.2. Configure the Management Interfaces for HTTPS
Issue description:
There is an extra dot in front of sentence ".CLI Command for Using a New Security Realm"
Suggestions for improvement:
Correct form is "CLI Command for Using a New Security Realm:"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 7 months