The purpose of this article is to provide a resolution for the provisioning error regarding setting up SCIM 2.0 with vSphere.
Setting up SCIM 2.0 VMware VSphere in Applications > Applications > Configure API Integration > Enable API Integration results in the error "Error authenticating: null"
- vSphere
- vCenter
- SCIM 2.0
- Network Architecture
- Provisioning
- Okta Identity Engine (OIE)
- Okta Classic Engine
Okta will only connect to SCIM servers that are publicly available. This error may occur if the vCenter SCIM server is behind a network firewall or is unavailable publicly on the internet for Okta to access.
The docs for vCenter's integration with Okta, mention the following:
"If your network is not publicly available, you must create a network tunnel between your vCenter Server system and your Okta server. After creating the network tunnel, use the appropriate publicly accessible URL as the Base Uri."
If Okta cannot reach the server because it is on the local network, a solution must be implemented within that network to make the SCIM server accessible on the public internet so Okta can make API requests to it. For any questions about how to set up a network tunnel, it is best to reach out to the service provider or team that operates and supports the SCIM server, the Network Devices involved, or both, to make the necessary changes to ensure this works accurately and securely with the Okta org.
