Python package aiohttp>=3.9.2 break azure-keyvault-certificates package's get_certificate functionality about aiohttp HOT 5 CLOSED

I don't see anything obviously wrong. But, the only thing that could have changed (as a result of the linked issue) is that it was expecting ssl previously, but actually not enabling ssl. Now it actually enables ssl, and you are missing certificates.

from aiohttp.

i.e. It may have been sending ssl=True somewhere, which was an invalid value before that change and actually disables ssl.

To fix your issue, install certificates so Python can find them (most installs do this by default), or use certifi as shown as an example in the docs.

from aiohttp.

Thanks @Dreamsorcerer for the quick turnaround.

We are not directly using aiohttp. We are using it via azure-keyvault-certificates from azure python sdk. Please check this issue that we have raised with them. We have directed your query to them.

from aiohttp.

I doubt someone here would be debugging a third party project. We need a pure-aiohttp reproducer to move forward.

from aiohttp.

We are not directly using aiohttp

Neither of my suggestions require direct use of aiohttp. Installing certificates globally is a normal thing that affects all of Python. And the project appears to have some way to specify the SSL context that gets passed to aiohttp if you need to use certifi instead.

from aiohttp.