Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: cn337131 <141730190+cn337131@users.noreply.github.com>
  • Loading branch information
tb06904 and cn337131 authored May 2, 2024
1 parent 3568489 commit 01d8a4b
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/administration-guide/gaffer-deployment/gremlin.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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", <id>)` step in the gremlin query.
`with("userId", <id>)` 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
Expand Down

0 comments on commit 01d8a4b

Please sign in to comment.