[JBoss JIRA] (ELY-439) Client Cert authentication using certificate passed from a proxy
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-439?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-439:
---------------------------------
Fix Version/s: 1.1.0.Beta6
(was: 1.1.0.Beta5)
> Client Cert authentication using certificate passed from a proxy
> ----------------------------------------------------------------
>
> Key: ELY-439
> URL: https://issues.jboss.org/browse/ELY-439
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: HTTP
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta6
>
>
> Undertow contains a feature where by the Proxy server can handle SSL and pass the certificate chain to Undertow - this is then used for the actual client cert authentication.
> We need to cover this type of scenario within our generic HTTP authentication framework.
> We could further wrap the SSLSession in a similar way Undertow does - or we could make the chain availbale as a fall back.
> Related to this we also need to work on the different attachment contexts, that may affect how we consider SSLSession attachments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ELY-428) HTTP Mechanism configuration during deployment
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-428?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-428:
---------------------------------
Fix Version/s: 1.1.0.Beta6
(was: 1.1.0.Beta5)
> HTTP Mechanism configuration during deployment
> ----------------------------------------------
>
> Key: ELY-428
> URL: https://issues.jboss.org/browse/ELY-428
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: HTTP
> Affects Versions: 1.0.2.Final
> Reporter: Pedro Igor
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.1.0.Beta6
>
>
> It should be possible to configure a HTTP mechanism during deployment in order to parse/load configuration and reuse it in subsequent requests to an application.
> The most common use case for that is around mechanisms that need to read some configuration from inside a deployment (or provided by the mech config) when it is being deployed to the server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ELY-458) Attachment and resource scopes for HTTP auth API
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-458?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-458:
---------------------------------
Fix Version/s: 1.1.0.Beta6
(was: 1.1.0.Beta5)
> Attachment and resource scopes for HTTP auth API
> ------------------------------------------------
>
> Key: ELY-458
> URL: https://issues.jboss.org/browse/ELY-458
> Project: WildFly Elytron
> Issue Type: Feature Request
> Components: HTTP
> Reporter: David Lloyd
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta6
>
>
> Add an API to provide access to attachment and resource scopes as follows:
> * Exchange/Request
> * Connection
> * Session
> * Application†
> * SSL Session
> * Global/JVM†
> Scopes marked with † can have access to resources as well.
> Scopes should also optionally support the registration of notifications so that a mechanism can be informed about the destruction of a specific scope.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month