[
https://issues.apache.org/jira/browse/GEODE-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582756#comment-15582756
]
Karen Smoler Miller edited comment on GEODE-1883 at 10/17/16 7:37 PM:
----------------------------------------------------------------------
There should be an update in the newly-added documentation about the client
setting of the properties. I will do this in the {{develop}} branch, and if
there must be a third Geode release candidate for 1.0.0-incubating, this change
should be cherry picked into the new release candidate.
Also, the documentation should be updated again if/when this bug is fixed.
was (Author: karensmolermiller):
There should be an update in the newly-added documentation about the client
setting of the properties. I will do this in the {{release/1.0.0-incubating}}
branch, so it goes into the next Geode release candidate.
> 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)
