The procedure to link [[Settings]] to pre-defined Invantive Cloud data container definitions is:
- Ensure the data containers are defined on Invantive Cloud, using the procedure [[From Local Definitions to Invantive Cloud]] or the Invantive Cloud form [[Database]].
- Ensure the checkbox "Allow Invantive Credentials Server Use" is checked.
- Ensure the public IP addresses are whitelisted on the database for the nodes that will use Invantive Credentials Server.
- Remove the locally defined data containers to relocate to Invantive Cloud from the settings file.
- Insert a data container of the `credentials` kind as documented in [[Settings]], using an Invantive Cloud service account.
## From Release 27.0 Onward
For example, an Exact Online data container is defined locally as the following entry in the `dataContainers` array of the database, and then registered on the Invantive Cloud database with URL Segment "my-exact-online":
```json
{ "kind": "dataContainer"
, "order": 10
, "alias": "eol"
, "provider": "ExactOnlineAll"
, "userLogonCodeMode": "Hidden"
, "passwordMode": "Hidden"
, "defaultUserLogonCode": "
[email protected]"
, "defaultPassword": "secret"
, "connectionString": "api-url=https://start.exactonline.nl;api-client-id=SOME-CLIENT-ID;api-client-secret=CLIENT-SECRET-VALUE;api-redirect-url=https://clientredirect.invantive.com;totp-secret=SOME-TOTP-SECRET"
, "allowConnectionStringRewrite": false
}
```
That entry is replaced by the following one, which covers all data containers of this Invantive Cloud database:
```json
{ "kind": "credentials"
, "order": 10
, "description": "My Exact Online"
, "databaseSegment": "my-exact-online"
, "dataContainers": "*"
, "userLogonCodeMode": "Hidden"
, "passwordMode": "Hidden"
, "defaultUserLogonCode": "
[email protected]"
, "defaultPassword": "secret"
}
```
Both entries live in the same `dataContainers` array of the database; the member `kind` states which of the two kinds an entry is.
## Up to and Including Release 26.0
In the XML format the same Exact Online data container is defined locally as shown below and then registered on the Invantive Cloud database with URL Segment "my-exact-online":
```xml
<database
order="10"
alias="eol"
provider="ExactOnlineAll"
userLogonCodeMode="Hidden"
passwordMode="Hidden"
defaultUserLogonCode="
[email protected]"
defaultPassword="secret"
connectionString="api-url=https://start.exactonline.nl;api-client-id=SOME-CLIENT-ID;api-client-secret=CLIENT-SECRET-VALUE;api-redirect-url=https://clientredirect.invantive.com;totp-secret=SOME-TOTP-SECRET"
AllowConnectionStringRewrite="false"
/>
```
The new section in the settings file would replace the existing local definition by all data containers of this Invantive Cloud database:
```xml
<credentials
order="10"
description="My Exact Online"
database="my-exact-online"
datacontainers="*"
userLogonCodeMode="Hidden"
passwordMode="Hidden"
defaultUserLogonCode="
[email protected]"
defaultPassword="secret"
/>
```