[JBoss JIRA] (ELY-221) Implement a better X.500 principal mapper
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-221?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-221:
----------------------------
Component/s: API / SPI
> Implement a better X.500 principal mapper
> -----------------------------------------
>
> Key: ELY-221
> URL: https://issues.jboss.org/browse/ELY-221
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: API / SPI
> Reporter: David Lloyd
> Fix For: 1.1.0.Alpha3
>
>
> We can provide something better than a flat string mapping. Some thoughts on requirements:
> * Require that a minimum set of keys are present, else return {{null}}
> * Allow piecewise assembly of principal names with the following components:
> ** Static string
> ** Single attribute value e.g. {{dc[0]}}
> ** Joined attribute value (with optional subrange) e.g. {{dc:"."}} would convert {{dc=example,dc=com}} to {{example.com}}
> ** Joined attribute value in reverse (with optional subrange)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (ELY-212) Client-side SSL context configuration is subtly wrong
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-212?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-212:
----------------------------
Component/s: Authentication Client
> Client-side SSL context configuration is subtly wrong
> -----------------------------------------------------
>
> Key: ELY-212
> URL: https://issues.jboss.org/browse/ELY-212
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.1.0.Alpha3
>
>
> SSL context client-side configuration is problematic in that the SSL context is not (and cannot be) cached. This means that we lose SSL session reuse and other benefits which may cause problems for users.
> However we also cannot just cache an SSL context on a configuration either - the client credentials may vary on each request, causing leakage between identities.
> What we need to do is have a separate SSL context client configuration mechanism, and use the generic client context configuration to reference this SSL context client configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (ELY-298) load-from/uri keystore xsd/parser mismatch
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-298?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-298:
----------------------------
Component/s: Authentication Client
> load-from/uri keystore xsd/parser mismatch
> ------------------------------------------
>
> Key: ELY-298
> URL: https://issues.jboss.org/browse/ELY-298
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Reporter: Kabir Khan
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Alpha3
>
>
> The xsd has
> {code}
> <xsd:complexType name="key-store-type">
> <xsd:sequence minOccurs="1" maxOccurs="1">
> <!-- Access source type -->
> <xsd:choice minOccurs="1" maxOccurs="1">
> <xsd:element name="file" type="name-type" minOccurs="1" maxOccurs="1"/>
> <xsd:element name="load-from" type="uri-type" minOccurs="1" maxOccurs="1"/>
> <xsd:element name="resource" type="name-type" minOccurs="1" maxOccurs="1"/>
> {code}
> The parser seems to look for 'uri' rather than 'load-from'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (ELY-278) Add CBH to AuthenticationConfiguration overriding *some* callbacks
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/ELY-278?page=com.atlassian.jira.plugin.sy... ]
David Lloyd updated ELY-278:
----------------------------
Component/s: Authentication Client
> Add CBH to AuthenticationConfiguration overriding *some* callbacks
> ------------------------------------------------------------------
>
> Key: ELY-278
> URL: https://issues.jboss.org/browse/ELY-278
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: Authentication Client
> Reporter: Kabir Khan
> Assignee: Kabir Khan
>
> SetPasswordCallbackHandlerAuthenticationConfiguration only allows overriding of PasswordCallback, CredentialCallback and CredentialParameterCallback. For OTP I need to handle PasswordCallback and ParameterCallback, as part of one class.
> SetCallbackHandlerAuthenticationConfiguration on the other hand seems to consider being the only callback, meaning for OTP I will not be able to reuse logic for handling the principal and the extended choice (added as ELY-274)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months