It's personal use here. The user is responsible to get his access token. It would be third party access when I handle authentication on my server, and generate access tokens for distribution to multiple users.
Many many many thanks jcl! That simplifies things a lot! So I think the user could enter the access token in the username field in Zorro UI or better, make an auxiliary application that stores the token in an encrypted file that is encrypted using username and password. Obviously, after accesing the token for the first time of running a 'Zorro session' the token is kept in memory so that I overcome the overhead of accesing a file. Are both approaches ok for Zorro BrokerLogin?
