[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.Beta5
(was: 1.1.0.Beta4)
> 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
> Fix For: 1.1.0.Beta5
>
>
> 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)
10 years, 2 months
[JBoss JIRA] (ELY-268) Review how mechanisms meet HttpAuthenticator
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-268?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-268:
---------------------------------
Fix Version/s: 1.1.0.Beta5
(was: 1.1.0.Beta4)
> Review how mechanisms meet HttpAuthenticator
> --------------------------------------------
>
> Key: ELY-268
> URL: https://issues.jboss.org/browse/ELY-268
> Project: WildFly Elytron
> Issue Type: Sub-task
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta5
>
>
> The current implementation is using a Supplier<List<HttpServerAuthenticationMechanism>> when get is called on this Supplier a ServerAuthenticationContext needs to be created, then all possible mechanisms need to be queried before the list of mechanisms is created.
> The HTTP Authenticator is created per request. API may be fine but we may need an easier way to provide all the mechanisms.
> Will look at that one later once hot deployment is also considered fully.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (ELY-261) Rework (and move) UsernamePasswordHashUtil
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-261?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-261:
---------------------------------
Fix Version/s: 1.1.0.Beta5
(was: 1.1.0.Beta4)
> Rework (and move) UsernamePasswordHashUtil
> ------------------------------------------
>
> Key: ELY-261
> URL: https://issues.jboss.org/browse/ELY-261
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI, Passwords
> Reporter: Darran Lofthouse
> Fix For: 1.1.0.Beta5
>
>
> Firstly this class is not really SASL specific so should be in a general util package.
> Secondly we now have password specs and a PasswordFactory - if this class still has a future then maybe it should be using those instead of it's own custom implementation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (ELY-355) HTTP Authentication Mechanism Testing
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-355?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-355:
---------------------------------
Fix Version/s: 1.1.0.Beta5
(was: 1.1.0.Beta4)
> HTTP Authentication Mechanism Testing
> -------------------------------------
>
> Key: ELY-355
> URL: https://issues.jboss.org/browse/ELY-355
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Testsuite
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta5
>
>
> We don't want to create a full HTTP server but we should have a sufficient wrapper to test the HTTP authentication framework and test out specific mechanims.
> This will leave the Elytron Web project to smoke test integration and not focus on testing the actual mechanisms.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months