qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
Date Fri, 12 Feb 2016 16:18:18 GMT

    [ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144776#comment-15144776
] 

ASF subversion and git services commented on QPID-7028:
-------------------------------------------------------

Commit 1730052 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1730052 ]

QPID-7028: [Java Broker] Allow the OAuth2 provider to specify an optional logout URI

* HttpRequestInteractiveAuthenticators are now responsible for producing a logout handler
to perform a redirect/forward after the logout
* OAuth2InteractiveAuthenticator logout handler redirects to an optional URI once Web Management
Console logout is complete.  This allows
  the user to be directed back into a page belonging to the overarching service

> [Java Broker] Add OAuth2 AuthenticationProvider
> -----------------------------------------------
>
>                 Key: QPID-7028
>                 URL: https://issues.apache.org/jira/browse/QPID-7028
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>            Reporter: Lorenz Quack
>         Attachments: 0001-OAuth2.patch, 0001-QPID-7028-Java-Broker-Improve-OAuth2.patch,
0001-QPID-7028-Java-Broker-OAuth2-improvements.patch, 0001-QPID-7028-OAuth2-Identity-Resolver-implementation-ca.patch,
0001-WIP-OAuth2-working-initial-refactor-complete.patch
>
>
> We want to provide the ability to login to the web management console with OAuth2. It
should be possible to use different OAuth2 backend (e.g., Google, CloudFoundry)
> Therefore it needs
> * pluggable way of setting the various parameters on the OAuth2 requests
> * pluggable way of getting the various parameters from the OAuth2 responses (e.g., access
grant, access token, refresh token, and expiry time, and user id)
> * those pluggable parts should have configurable addresses
> * configurable trust store for the OAuth2 servers
> * the client secret should be marked as "secure"
> * It should use (if available) a check_token or check_id service to get a user id to
use for ACL / logging purposes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message