# Issues Authenticating with Okta SDK

**URL:** <https://devforum.okta.com/t/issues-authenticating-with-okta-sdk/34008>\
**Category:** API\
**Created:** [July 22, 2025, 5:55pm UTC](https://devforum.okta.com/t/issues-authenticating-with-okta-sdk/34008 "2025-07-22T17:55:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chris.clewell](https://avatars.discourse-cdn.com/v4/letter/c/f05b48/32.png) [@chris.clewell](https://devforum.okta.com/u/chris.clewell)\
**Post date:** [July 22, 2025, 5:55pm UTC](https://devforum.okta.com/t/issues-authenticating-with-okta-sdk/34008/1 "2025-07-22T17:55:51Z")

</div>

Hello,  
I am having issues authenticating with the Okta SDK API tooling. I have success using direct URL API but when I try to use the SDK Client Config, no dice. I am getting the below error:

```auto
Cannot connect to host openly.okta.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1000)')]

```

My Client Config is:

```auto
config = {
    'orgUrl': OKTA_ORG_URL ("https://MY_ORG.okta.com"),
    'token': OKTA_API_TOKEN,
}

```

Any help would be amazing, I’ve hit a wall trying to use the SDK which would be much faster than building full urls for scripts

---

<div class="post-metadata">

**Author:** ![krishna](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@krishna](https://devforum.okta.com/u/krishna)\
**Post date:** [July 23, 2025, 12:23pm UTC](https://devforum.okta.com/t/issues-authenticating-with-okta-sdk/34008/2 "2025-07-23T12:23:49Z")

</div>

The most likely culprit is that your firewall is blocking ports (Due to local certs  
), specifically port 443, for that application. Check to ensure all necessary ports are allowed. See this [https://stackoverflow.com/questions/51925384/unable-to-get-local-issuer-certificate-when-using-requests](https://stackoverflow.com/questions/51925384/unable-to-get-local-issuer-certificate-when-using-requests) I don’t think it’s due to Okta, assuming your configuration is correct.

This uses python - albeit the issue should be similar [https://stackoverflow.com/questions/77442172/ssl-certificate-verify-failed-certificate-verify-failed-unable-to-get-local-is](https://stackoverflow.com/questions/77442172/ssl-certificate-verify-failed-certificate-verify-failed-unable-to-get-local-is)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/oktadev/original/1X/589c4c5f80de422d01f47cee7185a7fb8227835c.png) [@system](https://devforum.okta.com/u/system)\
**Post date:** [August 22, 2025, 12:24pm UTC](https://devforum.okta.com/t/issues-authenticating-with-okta-sdk/34008/3 "2025-08-22T12:24:47Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.