Controlling Script Passwords

By default, the BlueZone Script Recorder will not allow passwords (sometimes referred to as hidden fields) to be captured and inserted into the script while the script is being recorded.  This feature is referred to as the Automatic Password Prompting feature.

What is the Benefit of this Feature?

The danger is that scripts that contain passwords, can be shared with other users.  Another user can then run a logon script created by a different person, and log onto a host as the author of the script.

How it Works

When the Automatic Password Prompting feature is enabled, when a hidden field is encountered during the record process, the password is not actually stored as part of the script.  Instead, the BlueZone Script Recorder automatically inserts an "Input Command" with the label "BlueZone Recorded Prompt", with the hidden attribute turned on.

Essentially this is the same as inserting a "prompt for password" command into the script in lieu of the actual password.

NOTE  In BlueZone Text Based Scripts, the actual command that is inserted into the script is different but the end result is the same.

The end result of using this feature is that when the script is run, and a hidden field is encountered, the script will prompt all users including the author (and anyone else who runs this script), for the password.

Turning Off This Feature

If you want BlueZone to capture and record passwords during the script record process, you as the Administrator, can change the way BlueZone handles the recording of hidden fields.  To accomplish this, you will have to turn off the Automatic Password Prompting feature.

This feature is controlled by the ShowLockedDialogs setting which is located in the  SETUP.INI file.  The SETUP.INI file is located in the BlueZone Distribution Image or BlueZone CD-ROM.

By default the ShowLockedDialogs setting in the SETUP.INI file is set to Yes.  To disable the Automatic Password Prompting feature, locate the ShowLockedDialogs=Yes statement, located toward the end of the [BZSettings] section, and change the Yes value to No.

IMPORTANT!  Any changes made to the SETUP.INI file, will only take affect after SETUP.EXE is run, and BlueZone has run through the installation process.

SEE  Click here to see a sample of the SETUP.INI file.

SEE  Creating a Distribution Image in Chapter 6 for more information on creating a distribution image.

This is a global feature and will affect all types of BlueZone scripting regardless of the script format, proprietary or text based.

SEE  BlueZone Scripts in the Introduction to BlueZone Scripting in this chapter for more information on types of BlueZone scripts.