[
https://issues.apache.org/jira/browse/GEODE-6781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938656#comment-16938656
]
ASF subversion and git services commented on GEODE-6781:
--------------------------------------------------------
Commit d83baf00a43391c6b317cfa1842c78f47078e0e0 in geode-native's branch
refs/heads/develop from Charlie Black
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d83baf0 ]
GEODE-6781: Switch from deprecated Authenticator to SecurityManager for
examples (#528)
* Have the authentication use a SecurityManager vs Authenticator.
* Bash script was stopping servers vs shutdown.
* No reason to destroy the region if we are deleting the data directory. Wait
for process to die before trying to delete the data directories.
> AuthInitialize example uses deprecated server-side object
> ---------------------------------------------------------
>
> Key: GEODE-6781
> URL: https://issues.apache.org/jira/browse/GEODE-6781
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Blake Bender
> Priority: Major
>
> There are two objects which can be used for auth in Geode, Authenticator and
> SecurityManager. Authenticator is deprecated, so our example code should be
> using a SecurityManager. It is not using a SecurityManager. We need to
> modify the gfsh command line in startserver.sh and startserver.ps1 for the
> AuthInitialize example to use `--j=-Dgemfire.security-manager=` rather than
> `--J=-Dgemfire.security-client-authenticator=`, remove the Authenticator
> implementation from example.jar and replace it with a SecurityManager
> implementation, and verify that the example is running and using our auth
> scheme on both client and server.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
