As I've stated elsewhere I think the real power will come from being able to script multiple sites at once. For that we need to be able to keep a list of the user's sites and his/her jwt token (we don't need to store passwords) for that site.
My plan (and I've begun work on that in the PR #6 is that this is a json file next to the dll. The json file stores the sites with (a) a key, (b) a url and (c) the token. I plan to encrypt the token for security using SecureString. The key is used by the user to refer to that site (instead of having to hammer out the url every time he/she wants to run a command).
As I've stated elsewhere I think the real power will come from being able to script multiple sites at once. For that we need to be able to keep a list of the user's sites and his/her jwt token (we don't need to store passwords) for that site.
My plan (and I've begun work on that in the PR #6 is that this is a json file next to the dll. The json file stores the sites with (a) a key, (b) a url and (c) the token. I plan to encrypt the token for security using SecureString. The key is used by the user to refer to that site (instead of having to hammer out the url every time he/she wants to run a command).