[jboss-jira] [JBoss JIRA] (ELY-160) Client authentication configuration by task

[David Lloyd (JIRA)]

     [ https://issues.jboss.org/browse/ELY-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd resolved ELY-160.
-----------------------------
    Fix Version/s:     (was: 1.1.0.CR1)
       Resolution: Rejected


> Client authentication configuration by task
> -------------------------------------------
>
>                 Key: ELY-160
>                 URL: https://issues.jboss.org/browse/ELY-160
>             Project: WildFly Elytron
>          Issue Type: Task
>          Components: API / SPI
>            Reporter: David Lloyd
>            Assignee: David Lloyd
>
> The authentication client needs support for multiple tasks, such as:
> * {{connection}} - the authentication configuration applies to the connection itself
> * {{request}} - the authentication configuration applies to activities interacting with services provided by the named peer
> * {{*}} - the authentication configuration applies to all matching tasks
> In this way, one can specify a separate configuration for initial connections versus normal requests on that connection.
> Furthermore, a new authentication configuration type should then be added which allows a task configuration to be inherited to another task.  For example:
> * {{useConfiguration("<referenced-task>"}} - could specify that my current authentication configuration for the matched task should use the configuration assigned to the referenced task, for example "connection", which would in turn mean that the connection credentials should be used (whatever they may be) for the given task/match criteria.
> This allows a simple default configuration which allows connection credentials to be used whenever they are available.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)