The other slightly weird thing is that I usually pass the mime length as
the "\x10" hex, but when I do this with the authentication method
(substitute this for the "16" in the message from the previous post), the
server throws an error "java.lang.ClassCastException: java.lang.String
cannot be cast to [B
".
I think these problems have to do with serialization on my end, but a bit
of clarification would be great!
Thanks again for the help.
Dave
On Friday, September 18, 2015 at 2:27:21 PM UTC-4, David Brown wrote:
>
> Hi guys,
>
> Almost done with the update, and things have gone pretty smoothly up until
> the authentication. As expected, when I run the server using the
> conf/gremlin-server-secure.yaml, I get the expected 407 challenge, and I
> respond with a message that looks like this:
>
>
> b'16application/json{"requestId":"c075a312-613d-4fea-a97c-97b1bae332ca","op":"authentication","args":{"sasl":"0stephen0password"},"processor":""}'
>
> I think this is what the authentication message should look like, and I
> was under the impression that it was configured to work out of the box with
> this user and pass. However, I get a 401 response from the server. Do I
> need to expressly create a user in the credentials graph? Or is there
> something else I am missing here?
>
> Thanks!
>
> Dave
>
>
>
> On Thursday, September 17, 2015 at 10:37:30 AM UTC-4, David Brown wrote:
>>
>> Will do!
>>
>> On Thursday, September 17, 2015 at 10:35:32 AM UTC-4, Marko A. Rodriguez
>> wrote:
>>>
>>> Hi David,
>>>
>>> After you update, can you please tell us your experience. As Stephen
>>> mentioned, this release is backwards compatible for "users," but for
>>> "vendors" (languages/systems), a few test case renames/etc. might cause a
>>> burp here and there.
>>>
>>> Thanks,
>>> Marko.
>>>
>>> http://markorodriguez.com
>>>
>>> On Sep 17, 2015, at 8:17 AM, David Brown <dave...@gmail.com> wrote:
>>>
>>> Congratulations! Time to update the clients.
>>>
>>> On Wednesday, September 16, 2015 at 1:17:24 PM UTC-4, Stephen Mallette
>>> wrote:
>>>>
>>>> Hello TinkerPoppers,
>>>>
>>>> TinkerPop is happy to announce the release of 3.0.1-incubating.
>>>>
>>>> TinkerPop 3.0.1-incubating (http://tinkerpop.incubator.apache.org/)
>>>>
>>>> Documentation
>>>> AsciiDoc documentation:
>>>> http://tinkerpop.incubator.apache.org/docs/3.0.1-incubating/
>>>> Full JavaDoc:
>>>> http://tinkerpop.incubator.apache.org/javadocs/3.0.1-incubating/full/
>>>> Core JavaDoc:
>>>> http://tinkerpop.incubator.apache.org/javadocs/3.0.1-incubating/core/
>>>> Distributions
>>>> Gremlin Console:
>>>> https://dist.apache.org/repos/dist/release/incubator/tinkerpop/3.0.1-incubating/apache-gremlin-console-3.0.1-incubating-bin.zip
>>>> Gremlin Server:
>>>> https://dist.apache.org/repos/dist/release/incubator/tinkerpop/3.0.1-incubating/apache-gremlin-server-3.0.1-incubating-bin.zip
>>>> Maven Central Repo: http://repo1.maven.org/maven2/org/apache/tinkerpop/
>>>>
>>>> 3.0.1-incubating should represent a straightforward update for nearly
>>>> all users.
>>>>
>>>> Those implementing the TinkerPop core API might notice issues around
>>>> tests in the suite that have been renamed (which cause problems for
>>>> OPT_OUT
>>>> annotations, if not corrected) and if implementations tested against
>>>> GraphComputer tests (in which case, see the new GraphProvider.Descriptor
>>>> annotation). The specifics of these are documented clearly in JIRA -
>>>> search for tags with the "breaking" label for 3.0.1-incubating. That
>>>> should get you on track fairly quickly.
>>>>
>>>> Please enjoy!
>>>>
>>>> Stephen
>>>>
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Gremlin-users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to gremlin-user...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/gremlin-users/9c489c6d-7f7d-47cf-89d2-bf9f385639da%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/gremlin-users/9c489c6d-7f7d-47cf-89d2-bf9f385639da%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
