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

AVEVA™ Operations Control connected experience

Log out

  • Last UpdatedNov 26, 2024
  • 3 minute read

AVEVA Operations Control with the connected experience supports two different sign out experiences: web based applications and desktop applications.

Note: These log out experiences are distinct from logging out of CONNECT. See "Log out of CONNECT" later in this topic.

Web based applications

All on-premises web applications accessed in a fully featured browser client support single sign out. With single sign out, when an on-premises web application is signed out, other running web applications in the same type of browser such as another browser instance or a different tab in the same browser instance, non-incognito, will be signed out.

Desktop applications

Single sign out is not supported in desktop-based Operations Control products. Desktop-based products typically include mission-critical HMI and SCADA applications, typically running more than one application on a control or engineering station. Also, engineering workflows often develop applications using one developer's account while testing them using a different user account without logging out of the design-time environments.

Desktop-based applications continue to use AVEVA Identity Manager log out.

  • When you sign out of a desktop application, you are only signed out of that specific desktop application. Other desktop applications will continue to run with their current signed in user. If you launch the desktop application again, you will be prompted to authenticate again.

  • If the session expires before you re-launch the application you will be required to authenticate again.

  • If another user signs into the application and you are still signed into other applications configured with the connected experience on the same node, you remain as the active user on the other applications.

  • Closing an application without signing out does not constitute a sign out. Only that instance of the application closes. The session is still active on-premises and on the CONNECT server. If you open a different application on the same node, your session is still active and you will be authenticated with Single Sign-On.

Log out of CONNECT

Logging out of an application—as opposed to simply closing the application, which does not constitute a log out—triggers log out from CONNECT. You also can log out of CONNECT directly by clicking the user profile icon in your application or browser title bar, then selecting Log Out or Sign Out depending on the term used in the application.

A dialog displays the list of accounts you are connected to if more than one is available. Typically, only one account will appear for most users. Select the account from which you wish to log out — even if only one account appears in the list.

AIM account log out

Note: If multiple accounts are listed, be sure to select the account with which you are actively using Operations Control products. Logging out of the wrong account will keep you logged into the federated account that you are using.

After logging out of CONNECT:

  • Your design-time application will close.

  • Your run-time application will run in read-only mode.

  • You can log back into CONNECT then re-start any closed applications or applications running in read-only mode.

Consult your product documentation for specific information.

In This Topic