You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cannot connect to host graph.windows.net:443 ssl:default [The specified network name is no longer available]
Starting data gathering phase 2 of 2 (collecting properties and relationships)
The system uses self-signed certificate for https requests.
Is there any work around here or any flag/switch to include for bypassing this?
The text was updated successfully, but these errors were encountered:
tejas-kand
changed the title
Issue: SSLCertVerificationError while connecting to graph,windows.net:443
Issue: SSLCertVerificationError while connecting to graph.windows.net:443
Dec 6, 2024
The authentication is successful using acess_token but upon gathering data I get the following error:
Starting data gathering phase 1 of 2 (collecting objects)
Cannot connect to host graph-windows.net:443 ss1:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_ FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1020)')]
cannot connect to host graph.windows.net:443 ss1:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ss1.c:1020)')]
Cannot connect to host graph.windows. net:443 ssi:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1020)°)]
Cannot connect to host graph-Windows.net:443 ssl: True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE VERIFY FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl. c:1020)')]
Cannot connect to host graph.windows.net:443 ssl:default [The specified network name is no longer available]
Starting data gathering phase 2 of 2 (collecting properties and relationships)
The system uses self-signed certificate for https requests.
Is there any work around here or any flag/switch to include for bypassing this?
The text was updated successfully, but these errors were encountered: