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

Michael Martell updated GEODE-2854:
-----------------------------------
    Description: 
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.


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



> 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
>
> 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.3.15#6346)

Reply via email to