Re: REST API and new authentication API

2018-04-10 Thread Alexey Kuznetsov
Dmitriy, Yes, sound reasonable to add "authenticate" command and require token for all subsequent commands. Will update issue description. On Tue, Apr 10, 2018 at 2:43 PM, Dmitriy Setrakyan wrote: > On Tue, Apr 10, 2018 at 12:28 AM, Alexey Kuznetsov > wrote: > > > Dmitriy, > > > > Yes, becaus

Re: REST API and new authentication API

2018-04-10 Thread Sergey Kozlov
Hi I a bit investigated the issue for REST authentication and found following approaches: 1. Add authenticate command providing sessions token by login and password. Any further requests will require that token. Advantages: - Small changes for REST requests (just add token parameter) Disadvantag

Re: REST API and new authentication API

2018-04-10 Thread Dmitriy Setrakyan
On Tue, Apr 10, 2018 at 12:28 AM, Alexey Kuznetsov wrote: > Dmitriy, > > Yes, because we have a command "Add new user" and this command can be > executed only with credentials of some "admin" user. > > It means, that in one command you need to specify name of new user and > "admin" credentials at

Re: REST API and new authentication API

2018-04-10 Thread Alexey Kuznetsov
Dmitriy, Yes, because we have a command "Add new user" and this command can be executed only with credentials of some "admin" user. It means, that in one command you need to specify name of new user and "admin" credentials at the same time. If you have any ideas how we can handle this - I will b

Re: REST API and new authentication API

2018-04-10 Thread Dmitriy Setrakyan
Alexey, are you suggesting that we have "newUser" as command parameter, while "user" is also a valid command parameter?  ⁣D.​ On Apr 10, 2018, 12:00 AM, at 12:00 AM, Alexey Kuznetsov wrote: >I looked into code and I think that we could do the following: > >1) Use user and password for authenti

Re: REST API and new authentication API

2018-04-10 Thread Alexey Kuznetsov
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

REST API and new authentication API

2018-04-09 Thread Alexey Kuznetsov
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