[
https://issues.apache.org/jira/browse/GEODE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065884#comment-17065884
]
ASF subversion and git services commented on GEODE-7851:
--------------------------------------------------------
Commit 578cb0756710cf18ba345e125601e057ec413ebf in geode's branch
refs/heads/feature/GEODE-6008b from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=578cb07 ]
GEODE-7851: Pulse Oauth Configuration (#4823)
Co-authored-by: Dale Emery <dem...@pivotal.io>
Co-authored-by: Joris Melchior <jmelch...@pivotal.io>
* create an OAuthSecurityConfig to configure spring using oauth
* add PULSE as one of the oauth-enabled-component, and if pulse is set to use
oauth, set the OAuthSecurityConfig as the active security profile
* use pulse.properties in the locator's working dir to externalize pulse
authentication provider configuration
> Pulse should support OAuth2 authorization code flow
> ---------------------------------------------------
>
> Key: GEODE-7851
> URL: https://issues.apache.org/jira/browse/GEODE-7851
> Project: Geode
> Issue Type: New Feature
> Components: docs, pulse
> Reporter: Jinmei Liao
> Assignee: Dale Emery
> Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> Instead of using username/password to log in to pulse, pulse should redirect
> to a configured authentication provider to get access token to login.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
