[JBoss JIRA] (ELY-444) AuthorizationIdentity and PermissionMapper
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-444?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-444:
---------------------------------
Fix Version/s: 1.1.0.Beta8
(was: 1.1.0.Beta7)
> AuthorizationIdentity and PermissionMapper
> ------------------------------------------
>
> Key: ELY-444
> URL: https://issues.jboss.org/browse/ELY-444
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: API / SPI, Realms
> Reporter: David Lloyd
> Fix For: 1.1.0.Beta8
>
>
> When we initially designed the PermissionMapper we went to certain lengths to avoid exposing details of the realm. But now as the API has evolved it is clear that the permission mapper will need access to more information. The AuthorizationIdentity (or perhaps another object which includes the AuthorizationIdentity) should be made available to the permission mapper.
> In addition, this object could be expanded to include more information about the authentication, for example mechanism-specific information, which can feed into the authorization decision and could be useful for other things. Examples include: authentication timestamp, mechanism name/kind, forwarding credentials, and other attributes which derive from the mechanism as opposed to the identity.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[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.Beta8
(was: 1.1.0.Beta7)
> 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.Beta8
>
>
> 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)
8 years, 5 months