-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNOW-1892848: Web Browser Auth doesnt need user to be passed but asserts it #2143
Comments
thanks for raising this and the PR too. The username is required for Please, provide |
I want to leave a +1 that having to specify the username is cumbersome especially when you are providing template code to others and they need to modify it before login in with externalbrowser. @sfc-gh-dszmolka could you elaborate on the threat you are trying to close with this assertion? |
@sfc-gh-dszmolka According to the Docs The web browser client is supposed to be where we are prompted for credentials, hard-coding the username in the script is counterintuitive to the point of having a web browser auth |
@sfc-gh-dszmolka Can we get an update on this? |
hi, nothing much to update from my end - thank you for your contribution in the PR, the team will review once they get to it. |
Web Browser Auth doesnt need user to be passed but asserts it anyway
When passing dummy variable, auth still fails to happen
This deviates from the behaviour of the JS SDK
PR
The text was updated successfully, but these errors were encountered: