CME Gateway

CME Globex Secure Logon Support

Overview

CME Gateway 7.18.39 and higher supports the CME Globex Secure Logon functionality. 

To use the new Secure Logon functionality, you must configure an AccessKeyID and a SecretKey for each order session on the CME Gateway, as well as enable Secure Logon via the UseSecureLogon parameter in hostinfo.cfg.

Until these new parameters are added and Secure Logon is enabled, your iLink sessions will continue to use the legacy password parameters to log in to the exchange. When the secure key pair parameters are configured, the legacy password parameters are ignored.  The Password and MSGWPassword parameters can be removed from hostinfo.cfg when you are ready to exclusively use the configured Secure Logon parameters.

Configuring CME Secure Logon on the CME Gateway

For a description of each hostinfo.cfg parameter, refer to the following table.

CME Gateway iLink Session Secure Logon Parameters
Parameter Description
AccessKeyID, MSGWAccessKeyID Sets the secure access API key used for logging in to the exchange. CGW and MSGW iLink sessions require separate, unique access key pairs (key and secret) from CME. This parameter is required for using CME Secure Logon. 
SecretKey, MSGWSecretKey Sets the secure access API key secret for logging in to the exchange. CGW and MSGW iLink sessions require separate, unique access key pairs (key and secret) from CME. This parameter is required for using CME Secure Logon. 
UseSecureLogon

Sets whether the CGW or MSGW iLink session on the CME Gateway uses the legacy iLink password parameters or the CME Secure Logon key pairs to log in to the exchange. The UseSecureLogin parameter must be configured on a per session basis. Valid values are:

  • true — Use the AccessKeyID and SecretKey parameters (Secure Logon key pair).
  • false — Use the Password and MSGWPassword parameters (legacy).

If UseSecureLogon=false for any session, the legacy password parameters will be used by that session if they are populated.

Hostinfo.cfg examples: CME Secure Logon

The secure key pair needs to be added to both Convenience Gateway (CGW) and Market Segment Gateway (MSGW) sessions on the CME Gateway.

CGW iLink session example

In order to configure the Access ID and Secret Key for Convenience Gateway (CGW) iLink sessions, add the highlighted parameters below to hostinfo.cfg for each CGW session:

[order_session_1]

Member=

Password=

iLinkPrimaryIP=

iLinkPrimaryPort=

UseSecureLogon=true

AccessKeyID=

SecretKey=

MSGW iLink session example

In order to configure the Access ID and Secret Key for Market Segment Gateway (MSGW) sessions, add the parameters highlighted below to hostinfo.cfg for each MSGW session:

[order_session_1_MSGW]

Member=

UseSecureLogon=true

MSGWAccessKeyID=

MSGWSecretKey=

MSGWSenderCompID=

MSGWPassword=

MSGWPort=

 

CGW and MSGW iLink session example

The following example shows an MSGW session configured as part of a CGW iLink session. In this case, secure key pairs need to be configured for both the CGW session and MSGW session.

[order_session_1]

UseSecureLogon=true

Member=

Password=

iLinkPrimaryIP=

iLinkPrimaryPort=

AccessKeyID=

SecretKey=

MSGWSenderCompID=

MSGWPassword=

MSGWPort=

MSGWAccessKeyID=

MSGWSecretKey=