"could not create SSL/TLS secure channel"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 254
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Sometime in the past 2 months my C# app suddenly started giving the "could not create SSL/TLS secure channel" error.
wether I use Windows.Web or System.Net neither seem to work, it was working fine beforehand though. But I didn't see any announcements or release notes about any changes to this so I'm not sure why it started randomly.
The WinRT Api (and the older UWP SDKs) are really limited, so I can't use System.Net.ServicePointManager.SecurityProtocol to manually specify a specific TLS version if that's what I'm supposed to have done.
was there a change I didn't see or wasn't announced?
This happens when I call any Api endpoint, I can still get the authentication code to call them, but I get the error every time I do anything else.
(if this isn't the right place to ask this then can you tell me what is please?)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start by comparing the successful authentication-code request with the failing API endpoint calls in Windows.Web and System.Net, then review the API's announcements or release notes for TLS changes. Done means identifying a documented API-side change or producing a reproducible explanation and guidance for the secure-channel failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100