geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-2854) GEODE REST API Docs Missing Authentication
Date Thu, 15 Jun 2017 22:18:00 GMT


ASF GitHub Bot commented on GEODE-2854:

Github user karensmolermiller commented on a diff in the pull request:
    --- Diff: geode-docs/rest_apps/ ---
    @@ -29,162 +31,233 @@ All Geode REST interface classes and required JAR files are distributed
as a WAR
     where _install-dir_ is the server installation directory and _n.n.n_ is a version number.
    -To enable the developer REST API service in Apache Geode, set the `start-dev-rest-api`
Geode property to `true` when starting a data node using either `gfsh` or the ServerLauncher
API. Setting this property to true on a data node will start up an embedded Jetty server and
deploy the REST developer API WAR file.
    +- [Enabling the REST API](#setup_config_enabling_rest)
    +- [Starting the REST API Service](#setup_config_starting_rest)
    +- [Implementing Authentication for the REST API](#setup_config_implementing_auth)
    +- [Programmatic Startup](#setup_config_implementing_auth)
    +# <a id="setup_config_enabling_rest" class="no-quick-link"></a>Enabling the
    +The REST API service for application development runs only on data nodes; you cannot
run the service on a locator.
    +To enable the Developer REST API service on a given server, set the `start-dev-rest-api`
    +to `true` when starting the data node to start an embedded Jetty server and deploy the
Developer REST
    +API WAR file on that node. Use either the `gfsh start server` command or the ServerLauncher
API to enable this property.
    --- End diff --
    To help me parse what is getting started and where with the property, can you add a comma
or reword the sentence?

> GEODE REST API Docs Missing Authentication
> ------------------------------------------
>                 Key: GEODE-2854
>                 URL:
>             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:
> 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'

This message was sent by Atlassian JIRA

View raw message