Hi, All,
I reworked Ignite Web Agent to use access token instead of account password. Ignite Web Agent README.txt updated, new ZIP with updated Web Agent uploaded to http://104.197.2.239/ Changes pushed to ignite-843 branch. There were 2 reasons to do it: 1) Security. One could configure Web Agent with configuration file and it is not secure to put password in plain text file. 2) We are going to implement generation of configuration file for Web Agent download. This file will be automatically filled with user e-mail, access token and web server address. With password it is simply impossible to do because we do not store them. 3) Token could be obtained (and regenerated if needed) on Web Control Center "Profile" screen. -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
Alexey,
It sounds like a good improvement. You should also provide a way to view the token on the "Load from Database" or SQL pop up windows that offer to download the "ignite-web-agent" zip file. Perhaps something like this: * You will need your security token to access Ignite web console. * To view your security token, click "here" Also, should we allow more than 1 security token per account? D. On Tue, Sep 8, 2015 at 1:20 AM, Alexey Kuznetsov <[hidden email]> wrote: > Hi, All, > > I reworked Ignite Web Agent to use access token instead of account > password. > > Ignite Web Agent README.txt updated, new ZIP with updated Web Agent > uploaded to http://104.197.2.239/ > > Changes pushed to ignite-843 branch. > > There were 2 reasons to do it: > > 1) Security. One could configure Web Agent with configuration file and it > is not secure to put password in plain text file. > > 2) We are going to implement generation of configuration file for Web Agent > download. This file will be automatically filled with user e-mail, access > token and web server address. With password it is simply impossible to do > because we do not store them. > > 3) Token could be obtained (and regenerated if needed) on Web Control > Center "Profile" screen. > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com > |
Dmitriy,
Good usability point, thanks. Tomorrow I will add reminder for security token on pop that offer to download the "ignite-web-agent" zip. On Tue, Sep 8, 2015 at 9:01 PM, Dmitriy Setrakyan <[hidden email]> wrote: > Alexey, > > It sounds like a good improvement. > > You should also provide a way to view the token on the "Load from Database" > or SQL pop up windows that offer to download the "ignite-web-agent" zip > file. Perhaps something like this: > > * You will need your security token to access Ignite web console. > * To view your security token, click "here" > > Also, should we allow more than 1 security token per account? > > D. > > On Tue, Sep 8, 2015 at 1:20 AM, Alexey Kuznetsov <[hidden email]> > wrote: > > > Hi, All, > > > > I reworked Ignite Web Agent to use access token instead of account > > password. > > > > Ignite Web Agent README.txt updated, new ZIP with updated Web Agent > > uploaded to http://104.197.2.239/ > > > > Changes pushed to ignite-843 branch. > > > > There were 2 reasons to do it: > > > > 1) Security. One could configure Web Agent with configuration file and it > > is not secure to put password in plain text file. > > > > 2) We are going to implement generation of configuration file for Web > Agent > > download. This file will be automatically filled with user e-mail, access > > token and web server address. With password it is simply impossible to do > > because we do not store them. > > > > 3) Token could be obtained (and regenerated if needed) on Web Control > > Center "Profile" screen. > > > > > > -- > > Alexey Kuznetsov > > GridGain Systems > > www.gridgain.com > > > -- Alexey Kuznetsov GridGain Systems www.gridgain.com |
Free forum by Nabble | Edit this page |