[JBoss JIRA] (ELY-341) PEM file format support
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-341?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-341:
---------------------------------
Fix Version/s: 1.1.0.Beta9
(was: 1.1.0.Beta8)
> PEM file format support
> -----------------------
>
> Key: ELY-341
> URL: https://issues.jboss.org/browse/ELY-341
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: KeyStores
> Reporter: David Lloyd
> Assignee: Pedro Igor
> Fix For: 1.1.0.Beta9
>
>
> We should add support for PEM formats for formats including (but not limited to):
> * X.509 Certificate
> * CSRs
> * CRLs
> * RSA and DSA Public and Private Keys
> * PKCS8 format Private Keys
> * DH parameters
> * ECDSA Public Key
> * EC Private Key
> * EC Parameters
> This API could be consumed by various utilities or by custom credential storage implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ELY-573) Programatic authentication
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-573?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-573:
---------------------------------
Fix Version/s: 1.1.0.Beta9
(was: 1.1.0.Beta8)
> Programatic authentication
> --------------------------
>
> Key: ELY-573
> URL: https://issues.jboss.org/browse/ELY-573
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.1.0.Beta9
>
>
> This is critical as it risks changing defined APIs and SPIs but we need to cover programatic authentication.
> It is however possible this is handled within the app server integration and not within our framework but we have two predominant cases: -
> - Servlet calls authenticate which means our mechanisms need to be triggered to challenge the client.
> - Servlet calls login with a username and password.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[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.1.0.Beta9
(was: 1.1.0.Beta8)
> 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
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta9
>
>
> 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
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ELY-376) Password policies
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-376?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-376:
---------------------------------
Fix Version/s: 1.1.0.Beta9
(was: 1.1.0.Beta8)
> Password policies
> -----------------
>
> Key: ELY-376
> URL: https://issues.jboss.org/browse/ELY-376
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI, Passwords, Realms
> Reporter: Darran Lofthouse
> Assignee: David Lloyd
> Fix For: 1.1.0.Beta9
>
>
> Probably needs a design discussion first but we need to review where password policies fit in to the overall solution.
> We may say that policy handling is really the responsibility of the actual realm implementation, after all items such as history are going to be very realm specific.
> However there may also be a case in the generic sense that where a modifiable realm is in use a policy is desired to cover the complexity of any passwords set on that realm.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months