Fixed dev docs for expected SASL value This was changed long ago on TINKERPOP-1600 but the docs went stale. Note that the byte array is still supported on 3.2.x. It goes away in 3.3.0.
Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/1518cc42 Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/1518cc42 Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/1518cc42 Branch: refs/heads/TINKERPOP-1489 Commit: 1518cc420cc35939aafae790ed79eedfe3751766 Parents: 8bb9908 Author: Stephen Mallette <[email protected]> Authored: Mon Jun 26 14:29:56 2017 -0400 Committer: Stephen Mallette <[email protected]> Committed: Mon Jun 26 14:29:56 2017 -0400 ---------------------------------------------------------------------- docs/src/dev/provider/index.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/1518cc42/docs/src/dev/provider/index.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/dev/provider/index.asciidoc b/docs/src/dev/provider/index.asciidoc index 39c235b..de8be1f 100644 --- a/docs/src/dev/provider/index.asciidoc +++ b/docs/src/dev/provider/index.asciidoc @@ -827,7 +827,7 @@ evaluated and is committed when the script completes (or rolled back if an error [width="100%",cols="2,2,9",options="header"] |========================================================= |Key |Type |Description -|sasl |byte[] | *Required* The response to the server authentication challenge. This value is dependent on the SASL authentication mechanism required by the server. +|sasl |String | *Required* The response to the server authentication challenge. This value is dependent on the SASL authentication mechanism required by the server and is Base64 encoded. |saslMechanism |String | The SASL mechanism: `PLAIN` or `GSSAPI`. Note that it is up to the server implementation to use or disregard this setting (default implementation in Gremlin Server ignores it). |========================================================= @@ -874,7 +874,7 @@ Gremlin Server are deployed, session state is not shared among them. |========================================================= |Key |Type |Description |saslMechanism |String | The SASL mechanism: `PLAIN` or `GSSAPI`. Note that it is up to the server implementation to use or disregard this setting (default implementation in Gremlin Server ignores it). -|sasl |byte[] | *Required* The response to the server authentication challenge. This value is dependent on the SASL authentication mechanism required by the server. +|sasl |String | *Required* The response to the server authentication challenge. This value is dependent on the SASL authentication mechanism required by the server and is Base64 encoded. |========================================================= '`eval` operation arguments' @@ -975,7 +975,7 @@ operation is available to clear the cache of a specific side-effect. [width="100%",cols="2,2,9",options="header"] |========================================================= |Key |Type |Description -|sasl |byte[] | *Required* The response to the server authentication challenge. This value is dependent on the SASL authentication mechanism required by the server. +|sasl |String | *Required* The response to the server authentication challenge. This value is dependent on the SASL authentication mechanism required by the server and is Base64 encoded. |========================================================= '`bytecode` operation arguments'
