Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Update: looks like the argument connection URL is not handled consistently with the connect command one, and the latter passes on user name that's entered in the prompt correctly.
So,
!connect (url) => prompt; the username on HS2 side is whatever is entered in the prompt beeline -u (url) => anonymous (no prompt) !connect (url);user=foo => foo beeline -u (url);user=foo => anonymous beeline -n foo -u (url with or without the user) => foo
I'm going to add support for extracting the user from the -u argument, similar to connect argument