[JBoss JIRA] (ELY-54) Support for stronger hashes as alternatives to MD5
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-54?page=com.atlassian.jira.plugin.sys... ]
Darran Lofthouse updated ELY-54:
--------------------------------
Fix Version/s: 1.2.0.Beta3
(was: 1.2.0.Beta1)
> Support for stronger hashes as alternatives to MD5
> --------------------------------------------------
>
> Key: ELY-54
> URL: https://issues.jboss.org/browse/ELY-54
> Project: WildFly Elytron
> Issue Type: Feature Request
> Reporter: Darran Lofthouse
> Fix For: 1.2.0.Beta3
>
>
> Presently Digest authentication is based on MD5 - however we should either update the mechanism or add new mechanisms to support the use of stronger hashes.
> As this library is used both client and server side installations that require the stronger hashes can just ensure the client and server have the latest version of this library - installations that still require interaction with MD5 will need to ensure that it is still available as a mechanism.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ELY-151) Ability to supply additional information during credential acquisition
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-151?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-151:
---------------------------------
Fix Version/s: 1.2.0.Beta3
(was: 1.2.0.Beta1)
> Ability to supply additional information during credential acquisition
> ----------------------------------------------------------------------
>
> Key: ELY-151
> URL: https://issues.jboss.org/browse/ELY-151
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: API / SPI, Passwords
> Reporter: Darran Lofthouse
> Fix For: 1.2.0.Beta3
>
>
> I think this is the final known gap in our credential acquisition and validation API/SPI.
> There are a couple of specifications that also allow for additional information to be used when obtaining a representation of a users credential, the most obvious being the session based variant of digest authentication where a nonce and cnonce are also incorporated.
> A second variant with two different modes of operation would be the realm associated with the digest credential, currently we assume it is tightly associated with the storage representation of the credential but it could also be the case that the mech is requesting it for a specific realm.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (ELY-138) Client timed logout options
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-138?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-138:
---------------------------------
Fix Version/s: 1.2.0.Beta3
(was: 1.2.0.Beta1)
> Client timed logout options
> ---------------------------
>
> Key: ELY-138
> URL: https://issues.jboss.org/browse/ELY-138
> Project: WildFly Elytron
> Issue Type: Task
> Reporter: David Lloyd
> Fix For: 1.2.0.Beta3
>
>
> It should be possible to configure a client-side authentication to auto-logout after either an absolute duration, or after some amount of idle time, or both.
> The client-side authentication cache, whatever form it takes, must be aware of usages to update the logout time, for idle timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months