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

4.0 version of the microsoft sqlclient not working on sites that does not have ssl #1400

Closed
musictopia2 opened this issue Nov 22, 2021 · 5 comments

Comments

@musictopia2
Copy link

When I use the 4.0 version of the microsofts sql client, it says it does not trust the authority. However, 3.0 worked fine. Is there a way to work without ssl for a website. Because many businesses if they are hosting locally and want others to access from the same network, they cannot have ssl.

@Wraith2
Copy link
Contributor

Wraith2 commented Nov 23, 2021

from the release notes

Changed Encrypt connection string property to be true by default. #1210 Read more

@JRahnama
Copy link
Contributor

@musictopia2, as @Wraith2 mentioned, the default value of Connection property Encrypt is changed to true. Please take a look at them and let us about the outcome.

@musictopia2
Copy link
Author

am i correct in assuming the actual connection string has to change (especially if a person is using it in wpf or even console app)? there are many apps out there that does not even use any cloud. not everybody can even afford to put everything to the cloud.

@ErikEJ
Copy link
Contributor

ErikEJ commented Nov 23, 2021

If you are updating the app by depending on SqlClint version 4, you should also be able to update the connection string in use. (Or at least manipulate it before it is actually used)

@JRahnama
Copy link
Contributor

@musictopia2 I am closing this issue as it does not seem an actual issue to us. You can simple add Encrypt=false to your connection string and continue as it was before. You also can keep Encrypt value to true and add TrustServerCertificate=true in connection string. Please feel free to reopen the issue if you think there is a part that we can change and provide a better solution to all users.

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

4 participants