March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-681) Hide private packages from generated javadoc.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-681?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-681: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > Hide private packages from generated javadoc. > --------------------------------------------- > > Key: ELY-681 > URL: https://issues.jboss.org/browse/ELY-681 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta30 > > > We may want two profiles so we can generate a full javadoc and a 'public' javadoc. > The 'public' javadoc should be the default one generated and should exclude the following packages: - > org.wildfly.security._private > org.wildfly.security.asn1 > org.wildfly.security.auth.realm > org.wildfly.security.auth.realm.* > org.wildfly.security.authz.jacc > org.wildfly.security.credential.store.impl > org.wildfly.security.security.digest > org.wildfly.security.http.impl > org.wildfly.security.security.keystore > org.wildfly.security.mechanism.oauth2 > org.wildfly.security.mechanism.scram > org.wildfly.security.password.impl > org.wildfly.security.password.util > org.wildfly.security.pem > org.wildfly.security.sasl > org.wildfly.security.sasl.* (Except util) > org.wildfly.security.util > org.wildfly.security.util_private > org.wildfly.security.x500 > org.wildfly.security.x500.cert -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-617) Review 'null' handling for MechanismConfiguration and MechanismRealmConfiguration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-617?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-617: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > Review 'null' handling for MechanismConfiguration and MechanismRealmConfiguration > --------------------------------------------------------------------------------- > > Key: ELY-617 > URL: https://issues.jboss.org/browse/ELY-617 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Fix For: 1.1.0.Beta30 > > > Javadoc states various NameRewriter instances will not be null, implementation suggests otherwise. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-659) Make all mechanism implementations final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-659?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-659: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > Make all mechanism implementations final > ---------------------------------------- > > Key: ELY-659 > URL: https://issues.jboss.org/browse/ELY-659 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Mechanisms, HTTP, SASL > Reporter: David Lloyd > Priority: Critical > Fix For: 1.1.0.Beta30 > > > It is very important to make all the mechanism implementations final. Relatedly, they should have no protected members. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-939) We need to be able to support standard KeyManager instances

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-939?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-939: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > We need to be able to support standard KeyManager instances > ----------------------------------------------------------- > > Key: ELY-939 > URL: https://issues.jboss.org/browse/ELY-939 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta30 > > > When using PKCS#11 we should not assume we can manipulate the private keys etc.. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-938) KeyStore in authentication client should not mandate an input source

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-938?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-938: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > KeyStore in authentication client should not mandate an input source > -------------------------------------------------------------------- > > Key: ELY-938 > URL: https://issues.jboss.org/browse/ELY-938 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta30 > > > Some keystores such as PKCS#11 are initialised without an InputStream. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-936) Complete equivalent of CLIENT_CERT authentication for SASL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-936?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-936: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > Complete equivalent of CLIENT_CERT authentication for SASL > ---------------------------------------------------------- > > Key: ELY-936 > URL: https://issues.jboss.org/browse/ELY-936 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta30 > > > This will likely extend outside of Elytron but track it here first. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-930) Support appending a CallbackHandler to the CredentialSources

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-930?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-930: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > Support appending a CallbackHandler to the CredentialSources > ------------------------------------------------------------ > > Key: ELY-930 > URL: https://issues.jboss.org/browse/ELY-930 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta30 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-937) SSLContext in authentication client has no trust configuration

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-937?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-937: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > SSLContext in authentication client has no trust configuration > -------------------------------------------------------------- > > Key: ELY-937 > URL: https://issues.jboss.org/browse/ELY-937 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta30 > > > Currently it requires on the system default so it is not possible to configure trusted certificate authorities. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-929) AuthenticationConfiguration uniqueness enhancements

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-929?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-929: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > AuthenticationConfiguration uniqueness enhancements > --------------------------------------------------- > > Key: ELY-929 > URL: https://issues.jboss.org/browse/ELY-929 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta30 > > > Apply some enhancements to AuthenticationConfiguration uniqueness. > * Add admonishing JavaDoc to {{useCallbackHandler}} to point out the importance of per-identity uniqueness of the callback handler > The following also may be possible and useful: > * Modify the {{AuthenticationConfiguration}} process to capture instances for {{Supplier}}-driven components at the time the configuration is used via the {{AuthenticationContextConfigurationClient}} > * Add a variation of {{useCallbackHandler}} which accepts a {{Supplier<CallbackHandler>}}, or a {{Function<T, CallbackHandler}} and a {{T}}, allowing constructor refs to be given -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-926) PKCS#12 support in CredentialStore with JDK-8005408

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-926?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-926: --------------------------------- Fix Version/s: 1.1.0.Beta30 (was: 1.1.0.Beta29) > PKCS#12 support in CredentialStore with JDK-8005408 > --------------------------------------------------- > > Key: ELY-926 > URL: https://issues.jboss.org/browse/ELY-926 > Project: WildFly Elytron > Issue Type: Bug > Components: Credential Store > Environment: JDK with JDK-8005408 > Reporter: Zoran Regvart > Assignee: Zoran Regvart > Priority: Minor > Fix For: 1.1.0.Beta30 > > > JDK with [JDK-8005408|http://bugs.java.com/view_bug.do?bug_id=8005408] changed the behaviour of PKCS#12 KeyStore so it will use SecretKeyFactory to convert from SecretKeySpec to SecretKey. So a SecretKeyFactorySpi implementation is needed to support PKCS#7 Data OID used when storing data as SecretKeys in the PKCS#12 KeyStore. > This relates to ELY-920 and the test failure on JDK 1.8.0_74. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017