"Invalid Client" when ServiceNow opens a new browser page for the VRA Login

[kmenze]

VRA 7.3, ITMS 3.0, ServiceNow Istanbul and default authentication.

With the VRA_VIDM login rule marked as active, whenever a user logs into ServiceNow, they are prompted immediately to log into VRA, they click OK on the prompt and are presented with another browser window (screen shot attached).  The error returned is as follows:

An error occurred during OAuth2 operation.  Please contact your administrator to resolve the issue.

{ "error": "invalid_request","error_description": "Invalid client" }

The user is never presented with the VRA Login page.

We currently have the VRA_VIDM rule selected as inactive due to this issue.  It appears as though ServiceNow is importing the VRA content, no errors from any of the Scheduled Import jobs aside from the occasional "no sensors defined" error.

[draymond10]

Did you run through the Client Registration on the "Integration - vRealize Automation" module?  WHat happens when you back to it?  I get the notification that it was already set...

[shaikabdul · Accepted solution]

Please clear vrasn.clientID and vrasn.clientSecret from system properties and do client registration again.

[batuhandemirdal]

Hi,

Have you restarted the server? Have you checked the web services? Do you have a local admin password?

[shaikabdul]

We are giving suggestion related with ServiceNow only, We have not done on server side. 

[CalsoftTechie]

Hi kmenze​

Confirm if clearing values from vrasn.clientID and vrasn.clientSecret from system properties and performing client registration once again works for you.

[kmenze]

We actually found the vrasn.clientID & vrasn.clientSecret properties without any values in them.  We performed the client registration again and now we are being appropriately re-directed to a VRA login page.

As I suspected before, the URL previously was incomplete.  Below is how the URL for the VRA login comes up now:

https://<vra server>/SAAS/t/<tenant>/auth/oauth2/authorize?response_type=code&client_id=<account specified during client registration>@vshpere.local&redirect_uri=https://<our servicenow>.service-now.com/vra_vidm_landpage.do

This resolved this issue.  Thank you.

[kmenze]

We did previously do the Client Registration, so, not entirely sure why those two properties had no values.

[CalsoftTechie]

May be client registration was not successful initially.