[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7028: - Fix Version/s: qpid-java-6.1 qpid-java-6.0.1 > [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 > Fix For: qpid-java-6.0.1, qpid-java-6.1 > > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7028: --- Attachment: 0001-QPID-7028-Java-Broker-Improve-OAuth2.patch > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7028: --- Attachment: 0001-QPID-7028-Java-Broker-OAuth2-improvements.patch improved error handling > [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-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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7028: --- Attachment: 0001-OAuth2.patch This patch implements QPID-7028, QPID-7029, QPID-7030, QPID-7031, QPID-7045, and adds a pluggable Google OAuth2 backend > [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-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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7028: --- Attachment: (was: 0001-OAuth2.patch) > [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-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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7028: --- Attachment: 0001-OAuth2.patch > [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-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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7028: --- Attachment: (was: 0001-OAuth2.patch) > [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-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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7028: --- Attachment: 0001-OAuth2.patch > [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-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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7028: - Attachment: 0001-QPID-7028-OAuth2-Identity-Resolver-implementation-ca.patch Identity resolver utilising Google's OAuth 2.0 userinfo endpoint > [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-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., goolge, > 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 logging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7028: - Description: 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 logging purposes. was: 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., goolge, 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 logging purposes. > [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-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 logging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7028: - Description: 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. was: 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 logging purposes. > [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-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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7028) [Java Broker] Add OAuth2 AuthenticationProvider
[ https://issues.apache.org/jira/browse/QPID-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7028: - Attachment: 0001-WIP-OAuth2-working-initial-refactor-complete.patch WIP including initial cloud foundry check_token plugin > [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-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., goolge, > 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 logging purposes. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org