You are viewing an old version of this page. View the current version.

    Compare with Current View Page History

    « Previous Version 7 Next »

    With Qube!, you have a choice of running jobs on the Workers in one of two ways:

    • Under proxy mode, all jobs execute as the designated proxy user, regardless of who submitted them. 
    • Under user mode, all jobs execute as the user specified in the job, either the user that submitted the job, or some other specified user. All processes executed and files created would then owned by that user.

    This is controlled with the proxy_execution_mode parameter.

    User mode on Windows

    Icon

    To run with a proxy_execution_mode set to user on Windows workers, the user passwords must first be registered with Qube!, and must be kept up-to-date as the user changes their password. For a user to register their password, they must open WranglerView, go to the Administration pulldown, then choose "Register Windows Password..."

    This is only required for farms with Windows workers and a proxy_execution_mode of "user". User proxy_execution_mode can be used on OS X and/or Linux without registering a password.

    User mode requires consistent user accounts

    Icon

    The user account must exist on the worker for "user" proxy_execution_mode to function correctly. This implies that a central authentication system (Active Directory, LDAP, NIS, etc.) exists and is properly functioning. The default "proxy" proxy_execution_mode has no such requirement, as it will run all jobs through the local account "qubeproxy."

    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.

    • Username: qubeproxy
    • Password: Pip3lin3P@$$wd

    In the case of Windows, for each job that runs on a Windows host the Worker must supply three pieces of information so that the operating system will allow it to initiate processes as another user:

    • Windows Domain
    • User login
    • User password (encrypted)
    • No labels