Service Bridge Registration Errors - 'Key Exhange Request failed..'

[samtrobo]

I am attempting to set up Service Bridge between 2 demo instances. While trying to connect the instances I am running into the following issue:

After creating the Consumer Registration in the provider instance I have followed the link in the email and created the Provider Connection record in the Consumer instance. First issue to note is that the 'Save' UI action appears not to work and I instead have to save by right-clicking the header (although this may just be related to the demo instances being slow-responding).

After saving the record the following error messages occur:

Following this, the 'Retry Key Exchange Request' and 'Connect to Provider' UI actions appear to do nothing so I am essentially stuck at this step.

My current set up with respect to users/accounts is the following:

- I am logged into both instances with my local admin accounts, same username/email/password

- In the Provider instance my account is associated with the company/account used in the Consumer Registration record, and I am listed as a contact in the account record.

- In the Consumer Registration record (in the Provider instance) I am listed in the Contact field

Just to clarify this is for the non-legacy Service Bridge (sn_sb_con & sn_sb_pro)

Any help is appreciated

[Maik Skoddow]

Hi @samtrobo 

please take a look on https://docs.servicenow.com/bundle/vancouver-platform-security/page/administer/key-management-framew... which explains how two instances have to be connected for being able exchanging crypto keys.

Maik

[SrdanMatijevic]

Hi @Maik Skoddow,

I think the error on the exchange of crypto keys is a red herring. The non-legacy version of Service Bridge should establish connection automatically between provider and consumer instances when following configuration steps as described here https://docs.servicenow.com/bundle/vancouver-service-bridge/page/product/tmt-service-bridge-2/concep...  

[SrdanMatijevic]

Try with different usernames. We once tried connecting two demo instances with the same usernames and it didn't work. We are not sure were the same usernames the cause of the problem or not but when we created new users we managed to get it working.
In the background, there are Service Bridge flows that are looking up users in both directions so there is a chance that something goes wrong there. In any case, it doesn't hurt to create separate users with different usernames. At the very least, it will minimize the chance of you doing something wrong somewhere when configuring the provider and consumer sides.

[pooja keshari]

Have you resolved this issue , please let me know I am also getting the same error.