1. Qube
2. Service Mode Authentication: User vs Proxy

Service Mode Authentication: User vs Proxy

...

1. Launch WranglerView on the Supervisor as an Administrator
2. Click on the Host/Worker Layout tab
3. Select the Worker(s) to configure, right-click, and choose "Configure on Supervisor..."
4. Set under the Worker (User) heading the following fields:
   Image Added

• • proxy_execution_mode to proxy
  • proxy_account to the account to run the jobs as (it is preferable to set this to a network account rather than a local one)
  • proxy_password to the encrypted password for the account. You can type it directly (it is masked as you type) or you can run
      qblogin --display proxy_account
    where proxy_account is the account name, and then enter the encrypted password this prints out.

...

1. Designate a proxy user account name. By default, Qube! creates a user called "qubeproxy," for example. This proxy account must exist on all workers, either as a local User Account, or as a network account, controlled by a centralized authentication domain (preferred).
   
   
2. Use qblogin with the --display option to output an encrypted password for the proxy user.
     qblogin --display user
   where user is the proxy user name.
   
   
3. Add the following settings to the Worker qb.conf or the Supervisor qbwrk.conf.
     proxy_account = user
   where user is the designated proxy user.
     proxy_password = pass
   where pass is the encrypted password output from qblogin.
     proxy_execution_mode = proxy
   
   
4. Remove enforce_password from supervisor_flags setting in the Supervisor qb.conf

Default

...

Proxy User Account

The installation of the qube-worker package creates a local user account named "qubeproxy". The default worker configuration is to run in proxy mode with the qubeproxy user name and password for the proxy user.

...