I looked into code and I think that we could do the following: 1) Use user and password for authentication. 2) Use newUser and newPassword for new authentication API (add, remove and update user). 3) Debug why sessionToken is null.
Created issues: https://issues.apache.org/jira/browse/IGNITE-8201 https://issues.apache.org/jira/browse/IGNITE-8202 I will try to implement them in a couple of days. On Tue, Apr 10, 2018 at 11:32 AM, Alexey Kuznetsov <akuznet...@apache.org> wrote: > Igniters, > > Recently new authentication API was added. > > I added support for it on REST, but several problems appeared: > > 1) "&ignite.login=login" and "&ignite.password=pwd" should be used for > credentials. > May be we should use "&user=user" and " &password=pwd " instead? > But this will lead to conflict with new authentication API: > For example add user: http://localhost/ignite?cmd=*adduser*&*user*= > sample&*password*=sample&ignite.login=ignite&ignite.password=ignite > > Any ideas how to resolve this? > > 2) For some reason when new authentication is enabled session toked > returned as null > {"successStatus":0,*"sessionToken":null*,"error":null,"response":"2.5.0"} > > Session token can be used instead of adding user name and password to > every request. > > Who can help with resolving this issue? > > -- > Alexey Kuznetsov > -- Alexey Kuznetsov
