You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2016/02/17 12:36:18 UTC

[jira] [Resolved] (QPID-7069) [Java Broker] Add CloudFoundry specific GroupProvider

     [ https://issues.apache.org/jira/browse/QPID-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lorenz Quack resolved QPID-7069.
--------------------------------
    Resolution: Fixed

looks good to me

> [Java Broker] Add CloudFoundry specific GroupProvider
> -----------------------------------------------------
>
>                 Key: QPID-7069
>                 URL: https://issues.apache.org/jira/browse/QPID-7069
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>            Reporter: Lorenz Quack
>             Fix For: qpid-java-6.0.1, qpid-java-6.1
>
>         Attachments: 0001-QPID-7069-Java-Broker-Add-CloudFoundry-specific-Grou.patch
>
>
> Add a GroupProvider that checks a [CloudFoundry service dashboard|http://docs.cloudfoundry.org/services/dashboard-sso.html#checking-user-permissions] to see whether a certain user (represented by an OAuth2 accessToken) has permission to manage a set of service instances.
> This allows for example to configure the broker in a way to allow different OAuth2 authenticated users to have access to different virtual hosts by providing an appropriate ACL that matches the GroupPrincipals.



--
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