Start and run WindowMaker

This section explains about the behavior of WindowMaker in Operations Control connected experience.

Work with WindowMaker in Operations Control connected experience

1. Launch WindowMaker.

   If you are launching WindowMaker for the first time on this node and no other Operations Control product was launched and authenticated on the same node before, then you are prompted to authenticate with AVEVA Identity Manager on a web browser or embedded browser (based on the choice that you have made while configuring Authentication tab in System Management Server of the Configurator). If you have already launched and authenticated WindowMaker on this node or launched and authenticated any other Operations Control product on the same node before, then you will be authenticated using Single Sign-On. For more information refer to Authenticate using AVEVA Identity Manager section.

2. Enter your email address that is registered with an CONNECT account to sign in to AVEVA Identity Manager and the respective password.

   Once you signed in successfully, if you are entitled to an Edge or Supervisory subscription WindowMaker shows the sign in information in the user profile found on the title bar. My profile will display the logged in user ID and the name of the CONNECT account.

   

3. If valid credentials are not provided, or authentication is canceled, then you will be prompted with an error message. Contact your CONNECT Administrator for the credentials and try to sign in again. WindowMaker will close once you click OK.

   

   • If you close the embedded browser login page that was launched to authenticate with AVEVA Identity Manager, the authentication failure dialog will be displayed immediately.

   • If you do not provide credentials or close the web browser that was launched to authenticate with AVEVA Identity Manager, the authentication failure dialog will be displayed after 3 minutes.

4. When WindowMaker is running successfully, a check is made for valid AIM and CONNECT refresh tokens.

   If a valid AIM token is received, and AVEVA Identity Manager is disconnected from CONNECT, on-premise functionality will work. You cannot access the CONNECT Industrial Graphics drive. You must sign in AVEVA Identity Manager to get the access to CONNECT Industrial Graphics drive.