Clarify that username is optional #10647
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added Lukasz, Alex, and Piotr since they started this discussion. I tested with DBeaver on 365 and I get "Connection property 'user' is required". I assume this is still the case even in the API (and not just implemented in the JDBC driver). Also note the CLI just uses the operating system user if nothing is supplied. In my opinion it should be required.
Also note .. even without authentication/authorization on plain HTTP, the web UI requires a username.