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

Get Started with AVEVA™ Operations Control

Embedded browser pop-up versus default browser

  • Last UpdatedJan 05, 2024
  • 2 minute read

Configuring the browser for authentication in Step 3a: Configure SMS Advanced, Authentication (optional) impacts single sign on (SSO) behavior. Two choices affect the user authentication experience across all Operations Control products with connected experience enabled.

  • Use your system default browser

  • Use an embedded browser pop-up

    Note: Whichever option you choose, closing either the full-featured browser or the embedded browser pop-up will not log you out of AVEVA Connect. Your session will persist unless you log out of the application.

Use the system default browser

With the system default browser selected, all Operations Control products rely on the default browser to manage single sign on (SSO).

  • SSO with browser-based applications including on-premises and cloud applications.

  • SSO with native desktop applications.

  • SSO between desktop and browser applications.

The order of operations is flexible. For example, you can open the default browser, authenticate to AVEVA Connect applications then run the desktop or on-premises web application. Or you can reverse this order of operations.

Default browser SSO behavior

  1. SSO is supported only on your system's default browser including one instance with multiple tabs or multiple instances.

  2. SSO is not supported when in the browser incognito mode.

  3. Clearing the browser cache will require re-authentication.

  4. SSO for each product launch opens the default browser which can interrupt the workflow of moving from one product to another.

  5. In some instances, the default browser might not automatically close after authentication, potentially blocking focus on the desired product window.

  6. AVEVA Operations Control connected experience does not control web browser capabilities subject to your organization's web browser policies. If your organization's browser restrictions block connected experience features, we recommend that you choose the embedded browser pop-up dialog configured in Step 3a: Configure SMS Advanced, Authentication (optional).

    If an unsupported browser, such as Internet Explorer, is your system's configured default browser or if no supported browser is installed, you should install and configure a supported browser.

    As an alternative, you can you choose the embedded browser pop-up dialog configured in Step 3a: Configure SMS Advanced, Authentication (optional).

Use an embedded browser pop-up

With the embedded browser pop-up configured, the authentication prompt will appear as a popup dialog within a browser.

  • SSO with an embedded browser pop-up is available only for desktop-based Operations Control products.

  • SSO between desktop and browser applications is not supported. Desktop and browser application authentication is treated as separate browser instances in the embedded browser pop-up.

    After you have authenticated to a desktop-based product, and you subsequently launch a web-based Operations Control product you will be asked to authenticate again on that web browser. After authenticating on the web browser, SSO will be available to you for all instances of the browser.

  • To run web applications in a full-featured browser installed on your system, authentication is required in that browser. Web applications subsequently launched will leverage the SSO session in that browser.

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