. 20 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 21 2 Environment-specific notes 23 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. . 20 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 21 2 Environment-specific notes 23 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. 22 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 23 2 Environment-specific notes 25 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. . 22 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 23 2 Environment-specific notes 25 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. . 22 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 23 2 Environment-specific notes 25 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. 22 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 23 2 Environment-specific notes 25 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. 24 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 25 2 Environment-specific notes 27 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. 24 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 25 2 Environment-specific notes 27 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. 24 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 25 2 Environment-specific notes 27 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-

. 24 1.4.2 Authenticating at web service logon . . . . . . . . . . . . . . . . . . . . 25 2 Environment-specific notes 27 2.1 Using the object-oriented web service (OOWS) . . . . . . . . . . . . . succeed, regardless of user name or password. This should of course not be used in a production environment. Generally, the mechanism by which clients are authenticated is configurable by way of the VBoxManage so make sure you test this before deploying it. One can override this behavior by setting the environment variable VBOX_PAM_ALLOW_INACTIVE which will suppress failures when unable to read the shadow pass-