You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (JIRA)" <ji...@apache.org> on 2016/10/17 16:16:58 UTC
[jira] [Commented] (GEODE-1883) AuthInitializer should be made
optional
[ https://issues.apache.org/jira/browse/GEODE-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582647#comment-15582647 ]
Jinmei Liao commented on GEODE-1883:
------------------------------------
Currently in peer to peer communication, security-auth-init is optional. But in client-server, it is still required. It's going to be a very involved change on the client side to make it optional in the current state of java client.
> 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)