[ 
https://issues.apache.org/jira/browse/GEODE-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583282#comment-15583282
 ] 

ASF subversion and git services commented on GEODE-1883:
--------------------------------------------------------

Commit f1df6fc5920d0d1eebd210e816e61ad44074d39d in incubator-geode's branch 
refs/heads/develop from [~karensmolermiller]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f1df6fc ]

GEODE-1883 AuthInitializer should be made optional

Documentation of how a cache client may set its credentials
for authentication is revised to no longer state that the
client can set the two security properties. When this
bug is fixed, the documentation should be revised again.


> AuthInitializer should be made optional
> ---------------------------------------
>
>                 Key: GEODE-1883
>                 URL: https://issues.apache.org/jira/browse/GEODE-1883
>             Project: Geode
>          Issue Type: New Feature
>          Components: management
>            Reporter: Swapnil Bawaskar
>
> {{AuthInitializer}} is the interface that a client must implement that 
> provides credentials that are verified by the server. The same interface is 
> also used for peer authentication. 
> In order to configure {{AuthInitialize}} any Geode property starting with 
> {{security-}} is passed through to the {{AuthInitialize.getCredentials}} 
> method.
> For simple authentication where only a username and a password are required, 
> users should not really be required to implement the AuthInitialize interface 
> in the presence of property passthrough. 
> Geode should detect {{security-username}} and {{security-password}} 
> properties in gemfire.security OR gfsecurity.properties file and use those 
> for authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to