System configuration parameters

System configuration parameters are defined in the infolink.conf file stored at <path-to-infolink>/conf/infolink.conf. The file is in JSON format and has the following structure. <path-to-infolink> is defined in the INFOLINK environment variable.


{
    "masterRepository": {
    ... parameters go here ...
    }
}

For example:


{
    "masterRepository": {
       "useDefaultEmbedded":"no",
	   "user":"infolink",
	   "connStr":"jdbc:sqlserver://10.10.56.4:1433",	   
	   "password":"bigsecret",
	   "databaseName": "infolink_master",
    }
}

Parameters that can defined in the masterRepository object:

useDefaultEmbedded: yes - to store metadata in the embedded database (not recommended for production); no - store metadata in an external database that is defined by connStr, user, password, databaseName properties
connStr: connection string to the server where the metadata database is stored. Do not specify the name of the database in the connection string, use the databaseName property.
user: username to connect to the metadata database
password: password to connect to the metadata database
databaseName: name of the database to store metadata
authenticationSessionInactiveTimeoutSeconds (type: string, default: “-1”): Timeout in seconds for user web session inactivity. If the session remains inactive for this duration, it will be invalidated. Use -1 to indicate a session that never expires.
httpResponseHeaderCSPAppend (type: string): add additional parameters to the built-in value of the “Content-Security-Policy” HTTP response header. For example, "frame-ancestors 'self' https://trusted.partner.com;"
httpResponseHeaders (type: JSONArray): adds custom HTTP response headers to all HTTP responses. The value must be an array of JSON objects where each object contains “name” and “value” attributes. For example:
```
"httpResponseHeaders": [
  {"name": "Strict-Transport-Security", "value": "max-age=31536000; includeSubDomains;"},
  {"name": "header2", "value": "value2"}
]
```