Could the authenticate user function be updated to accept a username and password

[amishcode]

Hi - would it be possible to update the authenticateuser() function so that it accepts a username and password and passes those automatically to the GISAID site (I think this could be done by passing them in the GET request that's already there)? This would allow authentication to occur directly from the function call rather than by having to separately enter the credentials in a browser window that pops up - but I'm not sure if there is some other restriction/reason that would make that not allowed or undesirable.

Thanks,
Amish

[sinabahram]

+1 to this ask. Understood if user/pass is not a best practice, but then is it please possible to download or copy/paste from the website an oAuth or similar token that can be used in code that must run in headless environments?

[lenorakepler]

I was able to run headless by installing and authenticating locally, then copying over the authentication token (.R_outbreak-info-token, located in the working directory) to the working directory on the cluster where I wanted the software to run.