LSF Web Services lsf client binary auth management

Current state:

The LSF Web Services lsf binary requires providing the username password and API url every time you authenticate.  While this is reasonable for your first authentication further authentications are needlessly complicated as the client already has a list of clusters it knows about including their names and API urls but still requires the user to enter the entire thing requiring a longer copy and paste, hand typing, or having saved the url as a variable somehow on their own.

Requested product improvement:

Adding a method to reauth to an already configured cluster without including the api url.

  lsf cluster logon --username <your_username> --url https://lws.example.org:8448 

I personally think that if only a single cluster has been configured and the user issues the lsf cluster login command it should default to the default cluster for the api url.  I also think it would be very user friendly to also then use the last username that was used for that cluster.  But that does change significantly how the lsf cluster login behavior works by default.

Alternately an additional lsf cluster command such as reauth could be a solution and would follow the same logic of reusing the username and api url for the default cluster.

Why:

While specifying the api url each time is perfectly acceptable when used programatically via the openapi or even the python bindings it is onerous for a regular user working interactively.  Particularly for information that it already stored by the lsf client.