# SCIM Connector Testing

**URL:** <https://devforum.okta.com/t/scim-connector-testing/31170>\
**Category:** SCIM\
**Created:** [November 12, 2024, 5:04pm UTC](https://devforum.okta.com/t/scim-connector-testing/31170 "2024-11-12T17:04:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![natetc](https://avatars.discourse-cdn.com/v4/letter/n/f1d935/32.png) [@natetc](https://devforum.okta.com/u/natetc)\
**Post date:** [November 12, 2024, 5:04pm UTC](https://devforum.okta.com/t/scim-connector-testing/31170/1 "2024-11-12T17:04:05Z")

</div>

While I am able connect to my SCIM API Service hosted on a production-like cloud machine from Okta I am still unable to connect to my development machine. I get connect timed out. I can connect to my development machine without issue from any other device. What is it that I am missing? I suspect it is because of me using a self-signed certificate in my development server. Is there a way to establish trust between Okta and my development server in regards to SCIM Provisioning? This is the error I get when I click Test Connector Configuration.

```auto
Please review the form to correct the following errors:
Error authenticating: Connect to [redacted domain]:443 [[redacted domain]/[redacted ip]] failed: connect timed out
The connector configuration could not be tested. Make sure that the URL, Authentication Parameters are correct and that there is an implementation available at the URL provided.

```

---

<div class="post-metadata">

**Author:** ![vk-giri](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/vk-giri/32/5178_2.png) [@vk-giri](https://devforum.okta.com/u/vk-giri)\
**Post date:** [December 3, 2024, 8:22am UTC](https://devforum.okta.com/t/scim-connector-testing/31170/2 "2024-12-03T08:22:37Z")

</div>

Hi,

Is the SCIM API Service in your development machine exposed to the internet? You can try testing this out from a different machine using postman or curl to check if that is able to connect or not.

---

<div class="post-metadata">

**Author:** ![natetc](https://avatars.discourse-cdn.com/v4/letter/n/f1d935/32.png) [@natetc](https://devforum.okta.com/u/natetc)\
**Post date:** [December 3, 2024, 11:31am UTC](https://devforum.okta.com/t/scim-connector-testing/31170/3 "2024-12-03T11:31:57Z")

</div>

Thank you so much for replying. I should have followed up on this and closed it. After the long and arduous task of eliminating all other possibilities I placed a second call to my ISP and demanded that my issue be escalated. I had already called them once and they told me nothing was blocking me. Once my ticket was escalated they finally told me what I suspected all along that ports 80, 443, 8080, 8443 among others were all blocked.

---

<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:** [December 4, 2024, 11:32am UTC](https://devforum.okta.com/t/scim-connector-testing/31170/4 "2024-12-04T11:32:16Z")

</div>

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