Configuring Customer Network
-
Perform the following configurations on Jive side:
Item Description Responsibility a. VPN Build a VPN of Jive to SharePoint Jive Hosting and Customer. b. Firewall Open the customer firewall to incoming calls from Jive Customer c. Routing When using a Reverse Proxy, make sure that the routing of traffic: Jive > Customer Firewall > Reverse Proxy > SharePoing is set properly. Customer When using ADFS (Claims auth), the routing should also include the ADFS in the routing chain: Jive > Customer Firewall > (Reverse Proxy ,if exists) > ADFS. Customer d. DNS SP hostname is set in the Jive’s DNS so it can be resolved when Jive is addressing SP. Jive Hosting team e. SSL Certificates SharePoint server certificate must be valid and include an intermediate certificate with Jive’s supported cyphers. -
Perform the following configuration on SharePoint side:
Item | Description | Responsibility | |
---|---|---|---|
a. | Firewall | Open the customer firewall to outgoing calls from SharePoint to Jive. | Customer |
b. | Routing | If using a Proxy on the SharePoint farm, make sure that the routing of traffic: SP-> Proxy->Firewall->Jive is set properly. | Customer |
c. | DNS | Jive’s hostname is set in the customer DNS so it can be resolved when addressed from SharePoint. | Customer |
d. | SSL Certificates | Jive server certificate must be valid. Intermediate certificate must be added to the JAVA key-store on the Jive instance. | Jive Hosting team |
e. | User mapping validation | Validate that the SharePoint Admin has provided the correct value for the field with which User Mapping is performed. | Customer |