An Okta System for Cross-domain Identity Management (SCIM) test connector configuration fails when the third-party SCIM server resides behind a network firewall. Network administrators must create a network tunnel via port 443 to make the server publicly accessible and resolve the error. When setting up SCIM 2.0 with third-party tools, Okta generates the following error messages:

Error authenticating: null

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.

The following image displays the authenticating null error message generated during the test connector configuration.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• System for Cross-domain Identity Management (SCIM) 2.0
• Provisioning
• Third-party tools

Okta only connects to SCIM servers that are publicly available via port 443. This error occurs if the third-party SCIM server resides behind a network firewall.

How is the authenticating null error resolved?

Create a network tunnel via port 443 to make the private network publicly accessible and update the Base URL to ensure Okta can make API requests to the server.

1. Create a network tunnel via port 443 to make the private network publicly accessible within the SCIM server's existing network infrastructure.
2. Enter the appropriate publicly accessible URL as the Base URL.
3. Contact the service provider or the internal network team for assistance with securely setting up the network tunnel.

Related References

• SCIM Connector Configuration Error "Connect timed out" During Test Connection in Okta