OData / OData/odataorg.github.io
HTTPS SSL Certificate for services.odata.org is bad
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 73
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
When attempting to connect to the services.odata.org site, using SSL, I get the following error:
This server could not prove that it is services.odata.org; its security certificate is from *.azurewebsites.net. This may be caused by a misconfiguration or an attacker intercepting your connection.
The SSL certificate for the services.odata.org appears to be the default certificate from Azure. Azure automatically enables HTTPS, and then uses a default certificate from *.azurewebsites.net.
Azure offers instructions on how to fix this. The details are documented here.
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
Start with the Azure SSL documentation linked in the issue and verify the certificate currently served by services.odata.org. Done means the site presents a certificate valid for services.odata.org instead of the default *.azurewebsites.net certificate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100