Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Edge HMI

TABLE OF CONTENTS

Configure Historian authentication

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedOct 21, 2026
  • 2 minute read

Studio Database Gateway supports two authentication modes. The mode selected in the Trend worksheet must match the gateway-wide AVEVA Historian Integrated Security setting. If they do not match, the gateway rejects the connection (see Historian connection errors in Troubleshoot your database).

Worksheet option

AVEVA Historian Integrated Security

Result

Use Specific User Name and Password

Cleared (default)

Allowed

Use Specific User Name and Password

Selected

Rejected

Use Gateway Credentials

Selected

Allowed

Use Gateway Credentials

Cleared (default)

Rejected

Use Specific User Name and Password

  1. Select Use Specific User Name and Password in the Historian dialog.

  2. Clear AVEVA Historian Integrated Security in Studio Database Gateway.

  3. Enter an account that is known to the Historian server and authorized to write to Historian.

  4. Use DOMAIN\user for a domain account or HISTORIAN_HOST\user for a local account on the Historian computer. .\user is accepted only when AVEVA Edge and Historian are on the same computer.

The Windows account of the gateway and of the runtime is not used in this mode.

Use Gateway Credentials

  1. Select Use Gateway Credentials in the Historian dialog.

  2. Select AVEVA Historian Integrated Security in Studio Database Gateway.

  3. The Windows account that runs the gateway authenticates with Historian. See the account table in Manually run Studio Database Gateway.

  4. The account must be known to the Historian server and belong to a Historian group. If Historian is on another computer, use the same domain, or the same account name and password on both computers.

    The setting applies to the whole gateway. One gateway cannot serve worksheets with specific credentials and worksheets with gateway credentials at the same time. To use both, run a second gateway on another TCP port.

    Recommendation: Use specific credentials when the gateway account cannot be reliably authorized by the Historian server, for example in a workgroup, when the runtime runs as Local System, or with IoT View.

    Credential protection: the Password field is masked. In the worksheet configuration file the password is encrypted. With Data Protection enabled, the user name and password are protected with the project Data Protection password (see Enable Data Protection to encrypt sensitive information). Between the runtime and the gateway, credentials are obfuscated but not encrypted unless Secure Channel is enabled.