Friend servers
| Administration Page | Application/Contract | Syracuse/Collaboration | Class | friendServers | Representation | friendServer |
|---|
This page describes the use and handling of friendly servers.
| Use of friendly servers | How to establish a friendly server connection |
The export profile tool extracts data from the mongodb administration database and creates the result of the export as a file on a volume created in a mongodb database, which is associated with another V12 node.js server. This allows a user connected on this server to import the data to the mongodb database. In order to secure this operation, it is necessary to describe this other V12 node.js server as a friendly server.
When the query page is displayed, a list of friendly servers appear with the following information:
Describes the friendly server.
Defines the URL used to connect on the friendly new node.js URL. Example: https://www.example.com:8888.
The friendly server requires authentication from the local server, which is done with a client certificate. See below for more details.
Assume you want to make a connection from Syracuse server 'A' to the friendly server friendserver on port 8888.
To do this, you need a certificate and a private key. In order to make the following text understandable, assume that the certificate is called client.crt and the associated private key is client.key.
On server 'A':
* Create an instance of the certificate entity from client.crt and client.key.
* Add an instance of the friendly server entity, and use https://friendserver:8888 (change this to the correct values) for the collaboration endpoint URL and the just created instance of the certificate entity for the client certificate field.
On the friendly server:
* Create an instance of the certificate entity from client.crt (without private key client.key) if necessary.
* There must be a connection in the instance of the Host entity for port 8888 with SSL and client authentication.
* Provide your own certificate with private key as server certificate and the instance of the certificate entity for client.crt (without private key client.key) for the client certificate.
The authentication for this connection will not be through the usual login screen (with user name and password) but with the common name from the certificate client.crt without any extra password.