- Optionally, if required, you can set some advanced settings in the RossTalk Plugin for additional Security.
- In the configuration file (Engine/Plugin/Config/BaseRosstalk.ini), there is an optional configuration group for "Security" settings, where you can enable or disable advanced security for the RossTalk Plugin.
- If you want to enable it, manually add the [Security] group to the configuration file.
- Enabled parameter, when set to true, enables advanced security, and when set to false, disables it.
- WhiteList parameter defines a coma (,) separated list of IP address that are allowed to send RossTalk messages to the Voyager machine.
Optionally, we have a custom security measurement that can be enabled to validate RossTalk commands coming from applications that can manually modify the RossTalk messages like Ross Dashboard.
You can enable the use of a custom shared Key between the origin endpoint and the Voyager system.
- KeyEnable parameter, when set to true, enables the usage of a Key parameter to validate incoming messages.
- Key parameter specifies the UTF-8 Ascii text to be used to validate the incoming messages – for example, "u9jcrHKAK9apGPF4".
(Note: please use standard ascii letters and numbers only. Avoid symbols, spaces, and special characters.)
- KeyWhiteList parameters specify an optional comma-separated list of IP addresses of origin endpoints that would not require a Key to validate the incoming messages. That could be useful, for instance, to enable Key validation for messages coming from a DashBoard system, but not require it for incoming messages coming from a Carbonite Switcher or any other device that can't customize RossTalk Messages.
To add the Key value to your RossTalk messages in Dashboard:
- Edit the RossTalk command in the oGScript Editor, and concatenate your RossTalk messages with ?key= and your key value. For example:
- Original: GPI 101:0
- New (with the Key): GPI 101:0?key=u9jcrHKAK9apGPF4