Service Bridge Registration Stuck in Work in Progress

tpoeckes
Giga Guru

I have two instances that I'm trying to setup with Service Bridge.  I have followed the documentation on https://docs.servicenow.com/bundle/washingtondc-service-bridge/page/product/tmt-service-bridge-2/tas...

 

I complete all the steps including step 6 with no errors.  The Provider registration is in the state of "Work in Progress".

I  looked at KB Article KB1584604 https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1584604#Onboarding_stuck_in_W...  Onboarding Registration task stuck in Work in Progress.

 

I don't have any oauth errors.  Does anybody know what else I can check?

1 ACCEPTED SOLUTION

I fixed it.  This is what I did.  I basically started over.

 

Provider

1) deleted consumer registration

2) deleted consumer connection

3) deleted provider record

4) delete oauth entries (application registries)

5) delete credentials

6) deleted remote systems

 

Provider

1) deleted provider connection

2) delete oauth entries (application registries)

3) delete credentials

4) deleted remote systems

 

The trick for me was when I click that "connect to provider" I'm logged on as the authorized user in both instances.  UserIDs have to be identical.

View solution in original post

3 REPLIES 3

Sumanth16
Kilo Patron

Hi @tpoeckes ,

 

First make sure that your Provider and Consumer applications are updated to the most current versions and that you have installed the Global Script Include as described in KB1225292.   Then take a look at the instructions under "Onboarding Registration task stuck in Work in Progress" in the Service Bridge Onboarding Troubleshooting article KB1584604.

 

Please mark it as helpful (or) correct if it helps.

 

Thanks & Regards,

Sumanth Meda

tpoeckes
Giga Guru

@Sumanth16  

I am on the same latest versions of service bridge 1.1.

Global script has been imported.

As I mentioned above I have looked that KB Article KB1584604 but I don't have any errors that they are describing.

I fixed it.  This is what I did.  I basically started over.

 

Provider

1) deleted consumer registration

2) deleted consumer connection

3) deleted provider record

4) delete oauth entries (application registries)

5) delete credentials

6) deleted remote systems

 

Provider

1) deleted provider connection

2) delete oauth entries (application registries)

3) delete credentials

4) deleted remote systems

 

The trick for me was when I click that "connect to provider" I'm logged on as the authorized user in both instances.  UserIDs have to be identical.