From 01d8a4b9bf45fb1fa480d50df6b5dd5fbd68c64c Mon Sep 17 00:00:00 2001 From: tb06904 <141412860+tb06904@users.noreply.github.com> Date: Thu, 2 May 2024 15:45:43 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: cn337131 <141730190+cn337131@users.noreply.github.com> --- docs/administration-guide/gaffer-deployment/gremlin.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/administration-guide/gaffer-deployment/gremlin.md b/docs/administration-guide/gaffer-deployment/gremlin.md index 2c3d61ecc2..2bd9bdacb7 100644 --- a/docs/administration-guide/gaffer-deployment/gremlin.md +++ b/docs/administration-guide/gaffer-deployment/gremlin.md @@ -162,8 +162,8 @@ provided by standard Tinkerpop. The GafferPop implementation provides a functional `Authoriser` class that will handle passing the authenticated user to the underlying Gaffer graph. -To activate user auth with the gremlin server you must provide the classes you -wish to use in the gremlin server's YAML file like so: +To activate user auth with the Gremlin server you must provide the classes you +wish to use in the Gremlin server's YAML file like so: ```yaml # This should be a deployment specific class @@ -182,7 +182,7 @@ Gaffer graph for fine grained security. !!! note The `GafferPopAuthoriser` will deny attempts to set the user ID via a - `with("userId", )` step in the gremlin query. + `with("userId", )` step in the Gremlin query. The `authenticator` should be a class specific to the auth mechanism for your deployment e.g. LDAP. An example class `ExampleGafferPopAuthenticator` is