SCIM Connector Testing

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.

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.

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.

1 Like

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.

1 Like

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