Known Issues and Limitations

The following limitations apply to using Configuration Hub:

  • Multiple users can log into the same server and make changes, but they must be different browser sessions.
  • Only the following browsers were tested for use with Configuration Hub and iFIX: Google® Chrome, Microsoft® Edge based on Chromium, Mozilla® Firefox, or Apple® Safari (MAC OS only).
    Note: Sometimes the MAC OS cannot resolve the system name. In this case, update the hosts file. Also, on the MAC OS, you will be required to manually install the Configuration Hub root certificate.
  • From a single browser session, a user can log into only one plugin at a time. For example, an iFIX node or Historian one.
  • For iFIX, you can only run Configuration Hub from a running SCADA node. View nodes/iClients will not be able to login to Configuration Hub.
  • For Historian, if only one machine remains in a mirror group, you cannot remove it.
  • If you install Configuration Hub and the Historian Web Admin console on the same machine, and use self-signed certificates for both of them, the login page for Configuration Hub does not appear. To prevent this issue, disable the domain security policies:
    1. Access the following URL: chrome://net-internals/#hsts
    2. In the Domain Security Policy section, in the Delete domain security policies field, enter the domain name for Configuration Hub, and then select Delete.
  • Configuration Hub cannot be installed on computers with machine names containing non-English characters.
  • Configuration Hub will display the number formats and strings as they appear on SCADA or Historian Server node. Changing the browser language will not have impact on the appearance of this data.
  • In the Connections Panel, group parameters do not support regional number formatting.
  • Only English alphanumeric characters values and the following symbols are supported in the client ID and client secret fields: "-><~!@#$%^&*?|"

  • When iFIX and Configuration Hub are on different computers and an error displays that the iFIX SCADA is not active or unable to retrieve locale information, ensure that iFIX is started and that SCADA is enabled. (If iFIX has Failover enabled, then only the Primary Node in Maintenance Mode can connect to Configuration Hub.) Also, make sure that both systems have same date and time.

  • Spaces are not supported in the model or iFIX tag names in Configuration Hub.

  • If Historian and iFIX are registered with the same Configuration Hub, the Historian Model editor will be disabled. In this case, you can use the iFIX model to create your model.

  • When multiple iFIX and Historian plugins are registered to Configuration Hub, all plugins should use same Proficy Authentication (UAA) Server Name. If the Configuration Hub or Proficy Authentication Server are part of a domain system, then Fully Qualified Domain Name (FQDN) name should be used for Server Name.
  • When iFIX is upgraded from a previous version of iFIX, sometimes the iFIX Register to Configuration link shows as non-trusted. You will need to delete the certificates and binding, and then recreate them using the iFixConfigServiceCertTool.exe tool (as an Administrator). As a final step to establish the trust, you would need to copy the certificate files (iFIX_OpcuaConfigServer.crt and iFIX_OpcuaConfigServer.key files) from the C:\Program Files (x86)\GE\iFIX\CFG\iFIX_OpcuaConfigService\pki folder into the C:\Program Files (x86)\GE\iFIX\web\conf directory, and restart iFIX.