// Bcc’ed user-list and added dev-list I think that having stubs for the functionality unavailable in Ignite confuses more people. If someone has extended Ignite’s functionality, as did Oleksandr, that’s great – but it’s up to them to also develop the necessary tooling. But I’ll be happy to hear other opinions.
Thanks, Stan From: Alexey Kuznetsov Sent: 22 мая 2018 г. 12:23 To: u...@ignite.apache.org Subject: Re: control.bat authentication support Stan, I think that we should add support for authentication in control.sh One more tool will confuse Ignite users. On Tue, May 22, 2018 at 3:53 AM, Stanislav Lukyanov <stanlukya...@gmail.com> wrote: Hi, Ignite doesn’t provide built-in support for authentication, so the built-in control.bat/sh also don’t have stubs for that. So yes, I guess you need to write your own tool. A tool like that would be pretty simple though – just start a client node, parse command line arguments and map them to the methods of the ignite.cluster(). Stan From: Olexandr K Sent: 17 мая 2018 г. 17:09 To: u...@ignite.apache.org Subject: control.bat authentication support Hi guys, I configured Ignite user/password authentication by adding custom plugin. It works fine in server/client nodes and visor but I can't find any auth support in control.bat I checked it's source code and don't see any place where I can provide credentials. Should I write my own control tool or how can I solve this? BR, Oleksandr -- Alexey Kuznetsov
