Jump to content

Problem with installing Workspace One Access connector - services wont start


Recommended Posts

Hi,

I have my Access up and running, but after I install the Access Connector, the Directory Sync and Auth Sync services are not running. There is only error "Service terminated unexpectedly"

When I navigate to Access Admin console page, I cannot see the connectors details there, its empty like new.

Connector version is 23.09

In log file for Directory Sync I found this error: com.vmware.vidm.eds.gateway.operations.EnterpriseServiceRegistrationManager - Unable to register EDS ScForbiddenException[Operation: POST -> https://my-access-appliance-hostname/SAAS/jersey/manager/api/enterpriseservices][Status:403] 

Can anyone help with this?

 

Link to comment
Share on other sites

  • 2 weeks later...
  • Replies 6
  • Created
  • Last Reply

Top Posters In This Topic

  • Employee

@ivan_531 is that the same env where you got issues creating OAuth tokens? Connector would also use tokens to communicate, is it working after you were able to create tokens now? To fully check on issues like that it would require a set of logs from Access and the Connector.

 

Link to comment
Share on other sites

  • 3 weeks later...
  • Employee
On 7/11/2024 at 3:31 AM, ivan_531 said:

Hi,

I have my Access up and running, but after I install the Access Connector, the Directory Sync and Auth Sync services are not running. There is only error "Service terminated unexpectedly"

When I navigate to Access Admin console page, I cannot see the connectors details there, its empty like new.

Connector version is 23.09

In log file for Directory Sync I found this error: com.vmware.vidm.eds.gateway.operations.EnterpriseServiceRegistrationManager - Unable to register EDS ScForbiddenException[Operation: POST -> https://my-access-appliance-hostname/SAAS/jersey/manager/api/enterpriseservices][Status:403] 

Can anyone help with this?

 

Hi Ivan,

I know I'm a little late to this thread, but in my experience, when I can't start Connector services, it's usually because the Connector can't reach outbound to the tenant to get the SSL cert from Access.  Does your Connector have outbound connectivity on 443?  Is there a proxy in between internal network and internet?  Since there hasn't been much activity on this thread, I'm assuming you got this sorted out, if not, let us know, we can try and help further.

Link to comment
Share on other sites

  • 1 month later...

The solution to the problem that works when I have this problem with customers.

1. Generate a new token for Omnissa Workspace ONE Access. (if you have this symptom, you need to re-generate the token, you can't use the token again)
2. You need to prepare the public keys of the Root, Intermediate certificates signing the FQDN address of Workspace ONE Access.

3. You choose the advanced installation of the Agent and upload the certs and the new key. It solves the problem in 99% of cases.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...