You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/15 20:49:00 UTC
[jira] [Commented] (GEODE-2854) GEODE REST API Docs Missing
Authentication
[ https://issues.apache.org/jira/browse/GEODE-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051037#comment-16051037 ]
ASF GitHub Bot commented on GEODE-2854:
---------------------------------------
GitHub user davebarnes97 opened a pull request:
https://github.com/apache/geode/pull/583
GEODE-2854: GEODE REST API Docs Missing Authentication
Reviews requested from: @mmartell, @jaredjstewart @karensmolermiller @joeymcallister
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davebarnes97/geode feature/GEODE-2854
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode/pull/583.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #583
----
commit a77860db9144985858888fb4bd90f27f3cd488e9
Author: Dave Barnes <db...@pivotal.io>
Date: 2017-06-15T20:43:41Z
GEODE-2854: GEODE REST API Docs Missing Authentication
----
> GEODE REST API Docs Missing Authentication
> ------------------------------------------
>
> Key: GEODE-2854
> URL: https://issues.apache.org/jira/browse/GEODE-2854
> Project: Geode
> Issue Type: Task
> Components: docs
> Reporter: Michael Martell
> Assignee: Dave Barnes
>
> The REST API docs don't document how to do authentication. Looks like HEAD params "security-username" and "security-password" are supported but undocumented in the REST API.
> There is a comment about REST auth in this link: https://geode.apache.org/docs/guide/11/managing/security/implementing_authentication.html
> Also, the docs seem to imply that you pass usr/passwd in the http headers such as 'security-username' and 'security-password'. However, it only works using HTTP Basic Authentication, which Spring must be translating on the server side into the 'security-username' and 'security-password' params.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)