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

AVEVA™ Engineering

Username Authentication for Active Directory (Windows) and Connect/AVEVA Licensing as a Service (LaaS)

Username Authentication for Active Directory (Windows) and Connect/AVEVA Licensing as a Service (LaaS)

  • Last UpdatedApr 22, 2025
  • 2 minute read

Username Authentication for Active Directory (Windows) and Connect/AVEVA Licensing as a Service (LaaS)

An administrator can make a project-wide setting to activate user authentication.

The purpose of this setting is to enable user authentication by Windows username (for on-premises configurations) or by email address (where cloud technology is used for Laas or CONNECT.)

In versions of Administration without provision for cloud-based identification, the Windows username must be stored on the Name attribute of the ULOGID element.

Identifying users in a cloud-based project requires the @ symbol to be added to the identity. However, the @ symbol is not supported by the Name attribute. Therefore, if you populate Name in a cloud-based environment, identification fails.

To address this situation, the Authnm attribute has been added to ULOGID. Authnm supports the @ symbol. But, if you populate only Authnm in an on-premises environment, identification fails.

To ensure successful identification in both on-premises and cloud environments, we recommend that you populate both Name and Authnm.

Note:
A future enhancement will harvest the email addresses to enable an administrator to send a single email to all logged on users, giving important information or instructions.

Related Links
TitleResults for “How to create a CRG?”Also Available in