Secret frameworks
http-header
Name |
default |
Description |
|---|---|---|
|
|
When set to true, this secret can be transmitted over an insecure HTTP connection. Setting this to true can expose your secret to others on the network, and is not advised for use outside of a private network. |
|
|
Use this secret with subdomains of the |
|
The name of the HTTP header to add, e.g. |
|
|
The |
|
|
Identifies this secret uniquely. This is taken from the INI file section header, .e.g. |
|
|
The actual secret value to pass in the header, such as an API token. |
Use an HTTP header to authenticate. A well known header is used to pass your secret to the server each time you fetch data from the server.
koordinates
Name |
default |
Description |
|---|---|---|
|
|
When set to true, this secret can be transmitted over an insecure HTTP connection. Setting this to true can expose your secret to others on the network, and is not advised for use outside of a private network. |
|
|
Use this secret with subdomains of the |
|
||
|
The |
|
|
Identifies this secret uniquely. This is taken from the INI file section header, .e.g. |
platform
Name |
default |
Description |
|---|---|---|
|
|
When set to true, this secret can be transmitted over an insecure HTTP connection. Setting this to true can expose your secret to others on the network, and is not advised for use outside of a private network. |
|
|
Use this secret with subdomains of the |
|
|
The |
|
Identifies this secret uniquely. This is taken from the INI file section header, .e.g. |
|
|
Your RiskScape Platform |
Use a WebDAV Token for accessing files stored in the RiskScape Platform.