External commands
As you may know, there are many opportunities to extend Cradle’s functionality, including using external commands. These commands can be triggered from user-defined start pages, or the user-defined phase hierarchy, or when you work with attributes inside items.
Commands can be made variable using Command Directives. Some of these can access the username, password and project code of the current user.
For example, the Command Directive $LOGIN is replaced by the string -login user,pwd,pcode where username is the current user’s Cradle username, pwd is the current user’s plain text password and pcode is the project code of the database that the current user is logged-in to.
The Command Directives $CUSER, $PASS and $PROJC are available for each of these components.
Because of the sensitivity of this information, you can control whether or not these Command Directives are active.
You do this using the file:
eci_config
Whis is found in the admin directory of the Cradle installation on the server (so the eci_config file that may exist in Cradle client installations on end users’ computers is ignored).
You can enable / disable various ‘sensitive’ Command Directives by editing this file in the Cradle installation on your ‘Cradle server’.
Note that many of the sensitive Command Directives are enabled by default, but $LOGIN is one of those that is not enabled!