Skip to content
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

dialect requires username password, which breaks using trusted credentials #44

Open
patter001 opened this issue Jun 5, 2018 · 3 comments

Comments

@patter001
Copy link

the create_connect_args requires username password in the connect string instead of allowing for trusted credentials. It should default to None for username and password if they are not in the connect string

@sandan
Copy link
Member

sandan commented Jul 18, 2018

@patter001 Could you elaborate more on "allowing for trusted credentials"?

@patter001
Copy link
Author

if the username/password are "None" then on windows, the next layer of code (its been a while I forget which piece) sees the None and instead attempts to use windows credentials. This allows for our higher level tools to query without having to prompt user for credentials or save in to the code.

@sandan
Copy link
Member

sandan commented Jul 21, 2018

By next layer of code do you mean the OdbcConnection? All it will do is pass it to the ODBC layer.

The username and password can be saved elsewhere and read into the code (environment variables, text files, etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants