July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-462) DirContext suppliing service to be used in LDAP realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-462?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-462: --------------------------- Summary: DirContext suppliing service to be used in LDAP realm (was: LDAP realm should use JNDI to obtain LdapContext) > DirContext suppliing service to be used in LDAP realm > ----------------------------------------------------- > > Key: ELY-462 > URL: https://issues.jboss.org/browse/ELY-462 > Project: WildFly Elytron > Issue Type: Task > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- > (requested by Darran on F2F) > UPDATE: There will be DirContext suppling service, which will be referenced by realm: > * return type ExceptionSupplier<DirContext> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-462) LDAP realm should use JNDI to obtain LdapContext

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-462?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-462: --------------------------- Description: -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- (requested by Darran on F2F) UPDATE: There will be DirContext suppling service, which will be referenced by realm: * return type ExceptionSupplier<DirContext> was: -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- (requested by Darran on F2F) NEW > LDAP realm should use JNDI to obtain LdapContext > ------------------------------------------------ > > Key: ELY-462 > URL: https://issues.jboss.org/browse/ELY-462 > Project: WildFly Elytron > Issue Type: Task > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- > (requested by Darran on F2F) > UPDATE: There will be DirContext suppling service, which will be referenced by realm: > * return type ExceptionSupplier<DirContext> -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-462) LDAP realm should use JNDI to obtain LdapContext

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-462?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-462: --------------------------- Description: -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- (requested by Darran on F2F) NEW was: -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- (requested by Darran on F2F) > LDAP realm should use JNDI to obtain LdapContext > ------------------------------------------------ > > Key: ELY-462 > URL: https://issues.jboss.org/browse/ELY-462 > Project: WildFly Elytron > Issue Type: Task > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- > (requested by Darran on F2F) > NEW -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-462) LDAP realm should use JNDI to obtain LdapContext

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-462?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-462: --------------------------- Description: -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- (requested by Darran on F2F) was: LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration. (requested by Darran on F2F) > LDAP realm should use JNDI to obtain LdapContext > ------------------------------------------------ > > Key: ELY-462 > URL: https://issues.jboss.org/browse/ELY-462 > Project: WildFly Elytron > Issue Type: Task > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > -LDAP realm should use JNDI to obtain LdapContext (as JDBC realm use datasource) - configuration of connection should be outside of Elytron configuration.- > (requested by Darran on F2F) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-587) SSLContext integration into DirContext supplier service

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-587?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-587: --------------------------- Component/s: (was: Realms) Description: * we already have a resource to define the SSLContext * we want use it for connection to LDAP * new resource should return an ExceptionSupplier<DirContext> * new resource should reference SSLContext resource / capability was: * we have a resource to define the SSLContext * we want a way to wire it in so it is used for connection to LDAP * new resource should return an ExceptionSupplier<DirContext> * new resource should reference SSLContext resource / capability Summary: SSLContext integration into DirContext supplier service (was: SSLContext from Elytron subsystem in LDAP realm) > SSLContext integration into DirContext supplier service > ------------------------------------------------------- > > Key: ELY-587 > URL: https://issues.jboss.org/browse/ELY-587 > Project: WildFly Elytron > Issue Type: Task > Components: SSL > Reporter: Jan Kalina > Assignee: Jan Kalina > > * we already have a resource to define the SSLContext > * we want use it for connection to LDAP > * new resource should return an ExceptionSupplier<DirContext> > * new resource should reference SSLContext resource / capability -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2042) Improve performance of Message#writeHeader

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2042?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2042: --------------------------- Fix Version/s: 3.6.11 > Improve performance of Message#writeHeader > ------------------------------------------ > > Key: JGRP-2042 > URL: https://issues.jboss.org/browse/JGRP-2042 > Project: JGroups > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.11, 4.0 > > > The following stacktrace, taken with JFR, is highlighting a CPU consumer which could be optimised. > {noformat}Stack Trace Sample Count Percentage(%) > java.util.IdentityHashMap.get(Object) 66 2.224 > org.jgroups.conf.ClassConfigurator.getMagicNumber(Class) 66 2.224 > org.jgroups.Message.writeHeader(Header, DataOutput) 66 2.224 > {noformat} > One idea could be to use an ad-hoc implementation of Map which takes advantage of the key being a {{Class}}. An interesting alternative would be to avoid the map lookup altogether, by having the Header expose a method like "writeMagicNumber(DataInput to)". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-587) SSLContext from Elytron subsystem in LDAP realm

by Jan Kalina (JIRA)

Jan Kalina created ELY-587: ------------------------------ Summary: SSLContext from Elytron subsystem in LDAP realm Key: ELY-587 URL: https://issues.jboss.org/browse/ELY-587 Project: WildFly Elytron Issue Type: Task Components: Realms, SSL Reporter: Jan Kalina Assignee: Jan Kalina * we have a resource to define the SSLContext * we want a way to wire it in so it is used for connection to LDAP * new resource should return an ExceptionSupplier<DirContext> * new resource should reference SSLContext resource / capability -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2043) Improve performance of Message#readHeader

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2043?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2043. ---------------------------- Resolution: Done The JMH test showed that average performance of header creation dropped from ~300ns (previous reflection-based approach) to ~25ns with the {{Constructable}} approach. This is almost the same as calling the constructor directly. > Improve performance of Message#readHeader > ----------------------------------------- > > Key: JGRP-2043 > URL: https://issues.jboss.org/browse/JGRP-2043 > Project: JGroups > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0 > > > A CPU hot spot highlighed by profiling via JFR: > {noformat}Stack Trace Sample Count Percentage(%) > java.lang.reflect.Constructor.newInstance(Object[]) 71 2.392 > java.lang.Class.newInstance() 71 2.392 > org.jgroups.Message.readHeader(DataInput) 71 2.392 > {noformat} > I'd have expected the reflective constructor to perform well on a recent JVM, but apparently it's not in this case. A theory is that the {{Class}} type being unknown makes this code harder to optimise; needs to be looked into. > It might be possible to patch the {{ClassConfigurator}} to provide instances of the required {{Header}} type rather than returning the class, and optimise that instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-405) Add a KeyStore implementation backed by LDAP

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-405?page=com.atlassian.jira.plugin.sy... ] Jan Kalina edited comment on ELY-405 at 7/13/16 7:50 AM: --------------------------------------------------------- >From [http://www.tldp.org/HOWTO/archived/LDAP-Implementation-HOWTO/certificates...]: * The certificationAuthority objectclass implements the authorityRevocationList, certificateRevocationList and cACertificate attributes. * The *inetOrgPerson* objectclass supports the *usercertificate* (binary) attribute. * You can also use the mix-in objectclass strongAuthenticationUser to add certificates to non inetOrgPerson entries. was (Author: honza889): >From [http://www.tldp.org/HOWTO/archived/LDAP-Implementation-HOWTO/certificates...]: * The certificationAuthority objectclass implements the authorityRevocationList, certificateRevocationList and cACertificate attributes. * The inetOrgPerson objectclass supports the usercertificate (binary) attribute. * You can also use the mix-in objectclass strongAuthenticationUser to add certificates to non inetOrgPerson entries. > Add a KeyStore implementation backed by LDAP > -------------------------------------------- > > Key: ELY-405 > URL: https://issues.jboss.org/browse/ELY-405 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SSL > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > > It is possible for private keys, public keys and certificates to all be stored in LDAP - this task is to create a Java KeyStore implementation that can work with this. > LDAP most likely will take a reasonable amount of configuration so it may not be possible to be purely provider based and instead this type of KeyStore may need to be manually configured and instantiated. > Properties could be passed in using the InputStream to initialise the KeyStore but that doesn't help where we may want to pass in factories for connecting to a remote LDAP server. > In addition to the usual keys and certificates the entry types as used for CredentialStore should also be considered. > The implementation should also support manipulation of the entries - in this case this may mean immediate updates to the directory. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-405) Add a KeyStore implementation backed by LDAP

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-405?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-405: -------------------------------- >From [http://www.tldp.org/HOWTO/archived/LDAP-Implementation-HOWTO/certificates...]: * The certificationAuthority objectclass implements the authorityRevocationList, certificateRevocationList and cACertificate attributes. * The inetOrgPerson objectclass supports the usercertificate (binary) attribute. * You can also use the mix-in objectclass strongAuthenticationUser to add certificates to non inetOrgPerson entries. > Add a KeyStore implementation backed by LDAP > -------------------------------------------- > > Key: ELY-405 > URL: https://issues.jboss.org/browse/ELY-405 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SSL > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > > It is possible for private keys, public keys and certificates to all be stored in LDAP - this task is to create a Java KeyStore implementation that can work with this. > LDAP most likely will take a reasonable amount of configuration so it may not be possible to be purely provider based and instead this type of KeyStore may need to be manually configured and instantiated. > Properties could be passed in using the InputStream to initialise the KeyStore but that doesn't help where we may want to pass in factories for connecting to a remote LDAP server. > In addition to the usual keys and certificates the entry types as used for CredentialStore should also be considered. > The implementation should also support manipulation of the entries - in this case this may mean immediate updates to the directory. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2016