Ebonding: Authorization & Security architecture

[Axis1]

We are working in ServiceNow to ServiceNow Ebonding and need suggestions on overall architecture & best practices for authorization & Security.

1. In ebonding, main network connectivity will be happening between two ServiceNow instances. How this connectivity will happen. Does it happen within ServiceNow cloud or it has internet exposure?

2. Any pros/Cons OR suggestions on setting up authorization especially for ebonding solution (Basic, OAuth, Certificate)?

[Ali543]

 In ebonding, main network connectivity will be happening between two ServiceNow instances Chicago limo service. How this connectivity will happen. Does it happen within ServiceNow cloud or it has internet exposure?

[ersureshbe]

Hi, connectivity - you answered above. If cloud tools integration example servicenow to servicenow no additonal effort. Its secured connection it will allow. If error persist your network team can answer it.

Authentication and Authorization - based on the tool. But the recommendation is oAuth. Cons can be classified by which tool you are integrating.

[Axis1]

For Connectivity, I see following scenario - considering two companies A & B  having two ServiceNow instances.

Here is how the network communication will flow:

1. USER A => ServiceNow Instance A ========> ServiceNow Instance B

2. USER B => ServiceNow Instance B ========> ServiceNow Instance A

Does this communication between two ServiceNow instance happen within ServiceNow Data center only OR the network goes through internet - which may need additional security considerations based on client requirements.