January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-88) Command line utilities

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-88?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-88: -------------------------------- Fix Version/s: 1.0.0.Beta1 > Command line utilities > ---------------------- > > Key: ELY-88 > URL: https://issues.jboss.org/browse/ELY-88 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: David Lloyd > Fix For: 1.0.0.Beta1 > > > We should provide easy-to-use command line tools from the Elytron JAR as a main class that provide useful functions to users like: > * Creating password hashes > * Creating certificates and certificate requests > * Creating key pairs of various types > * Managing key stores (everything keytool does) > * Get the library version -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-12) Interoperability Testing with PicketLink

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-12?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-12: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Interoperability Testing with PicketLink > ---------------------------------------- > > Key: ELY-12 > URL: https://issues.jboss.org/browse/ELY-12 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-128) RFC 5843 additional hash types for Digest authentication, applied to SASL

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-128?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-128: --------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > RFC 5843 additional hash types for Digest authentication, applied to SASL > ------------------------------------------------------------------------- > > Key: ELY-128 > URL: https://issues.jboss.org/browse/ELY-128 > Project: WildFly Elytron > Issue Type: Enhancement > Components: SASL > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > http://tools.ietf.org/html/rfc5843 specifies three additional SHA-based digest schemes. Apply these to SASL. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-124) Java 8+ supports unbound SASL servers; GSSAPI and DIGEST-MD5 both use this value

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-124?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-124: --------------------------------- Fix Version/s: 1.0.0.Beta1 > Java 8+ supports unbound SASL servers; GSSAPI and DIGEST-MD5 both use this value > -------------------------------------------------------------------------------- > > Key: ELY-124 > URL: https://issues.jboss.org/browse/ELY-124 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > Since Java 8, the SaslServerFactory interface has been changed so that the serverName may be null. If null, the server name is considered "unbound" and the client can select what server name it wants to use. > The release notes say: > {quote} > SASL service for multiple host names: When creating a SASL server, the server name can be set to null to denote an unbound server, which means a client can request for the service using any server name. After a context is established, the server can retrieve the name as a negotiated property with the key name SASL.BOUND_SERVER_NAME. See RFE 7110803. > {quote} > The updated JavaDoc says: > {quote} > serverName - The fully qualified host name of the server to authenticate to, or null if the server is not bound to any specific host name. If the mechanism does not allow an unbound server, a SaslException will be thrown. > {quote} > The RFE link is: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7110803 > The two SASL mechanisms in Elytron that would be impacted by this are DIGEST-MD5 and GSSAPI. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-121) Background initialization/pooling of SecureRandom

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-121?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-121: --------------------------------- Fix Version/s: 1.0.0.Beta1 > Background initialization/pooling of SecureRandom > ------------------------------------------------- > > Key: ELY-121 > URL: https://issues.jboss.org/browse/ELY-121 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Utils > Reporter: David Lloyd > Priority: Minor > Fix For: 1.0.0.Beta1 > > > Provide a facility to initialize and pool SecureRandom instances in a background thread so that when things like SSLContexts are initialized, there are ready SecureRandoms. A background daemon thread which simply feeds instances into a modestly-sized BlockingQueue is probably more than adequate. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-22) Expand LDAP realm to support RFC3112

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-22?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-22: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Expand LDAP realm to support RFC3112 > ------------------------------------ > > Key: ELY-22 > URL: https://issues.jboss.org/browse/ELY-22 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > RFC3112 adds a new attribute 'authPassword' and can be used to store passwords in various formats. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-60) Update the local authentication mechanism to allow permissions to be specified for the challenge file.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-60?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-60: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Update the local authentication mechanism to allow permissions to be specified for the challenge file. > ------------------------------------------------------------------------------------------------------ > > Key: ELY-60 > URL: https://issues.jboss.org/browse/ELY-60 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > (This would include switching to a dependency on Java 7 server side at least) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-19) Add KeyCload based realm implementation.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-19?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-19: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Add KeyCload based realm implementation. > ---------------------------------------- > > Key: ELY-19 > URL: https://issues.jboss.org/browse/ELY-19 > Project: WildFly Elytron > Issue Type: Sub-task > Reporter: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-31) Authentication and establishment of IdentityContext based on authorization ID.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-31?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-31: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Authentication and establishment of IdentityContext based on authorization ID. > ------------------------------------------------------------------------------ > > Key: ELY-31 > URL: https://issues.jboss.org/browse/ELY-31 > Project: WildFly Elytron > Issue Type: Sub-task > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > This may be our most critical scenario, ELY-30 is really a simplification of this one. > Being able to establish an identity as a different user is a key feature we are looking to achieve as this is going to be a fundamental requirement for the identity switching and propagation capabilities. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-24) Add support to verify a password to LDAP realm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-24?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse updated ELY-24: -------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha1) > Add support to verify a password to LDAP realm > ---------------------------------------------- > > Key: ELY-24 > URL: https://issues.jboss.org/browse/ELY-24 > Project: WildFly Elytron > Issue Type: Sub-task > Components: Realms > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > This is to add support to take a clear text password and use it to connect to LDAP to verify the users identity. > _Note: This is provided for legacy purposes rather than as a preferred solution. Ideally either one of the solutions which retrieves the password from LDAP would be used or GSSAPI depending on the overall architecture._ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

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 January 2015