Allow generation of tokens via a REST endpoint by supplying username/password/expiry as parameters. This is similar to the now deprecated fme token service.
When trying to automate some workflows that include FME Server jobs through scripting (e.g. using Powershell), currently the only recommended way to generate a token for REST API calls is to manually create an API token via the web interface. This doesn't fit well with automation and also involves storing/using a long-lived token, which is potentially insecure. The only other documented way to generate a token is to first use Basic Authentication, before creating a token, which is definitely insecure as user/password are sent in plain text.
If there was a "generateToken" endpoint with user/password/expiry parameters that supported HTTPS and POST only (similar to the ArcGIS Server approach) this would be a secure way of generating a short-lived token for subsequent API calls.
