Use this action to send a password back to the managed host that sent the message that was matched. You specify the password as the action text in readable form, but it is stored in the database in an unreadable form. Test, Trace, and Debug modes do not echo the action text to the log files, and DADB does not convert the action text to readable form in the source file it produces.

You cannot use this action for a UNIX or other ANSI X3.64 connected system for which spo_ping monitoring has been defined.

See 4.2 for formatting information. The action-textis a password or other command. It must be enclosed in quotes.

Requirement for Initializing MCP Automation   

Inclusion of a PASSWORD action in the active autoaction database is required for initializing the automation of MCP systems through Operations Sentinel. SP-AMS matches MCP connection requests to patterns specified in the database.

MCP Example

Automation of MCP systems requires that a pattern similar to the one in this example be included in the autoaction database. This is needed to comply with the MCP security requirement for a usercode and password. The leading % character is needed to completely hide the usercode and password.

DEFINE "C2"
		MESSAGE \
	"SINGLE POINT AMS AUTOMATION STARTED
   USING DATABASE db FOR SYSTEM hostid."
		TOKEN KEYWORD 4 "AUTOMATION"
		TOKEN FIXED 3 "AMS"
		TOKEN FIXED 5 "STARTED"
		ACTION PASSWORD "%user-code/password"
END

UNIX Example

This example matches the password prompt from UNIX system DP23 and sends the console password "oper-01A" to the system:

DEFINE "LOGIN-MSGS"
   MESSAGE "Password:"
   TOKEN KEYWORD 1 "Password:
   TOKEN HOSTID "DP23"
   ACTION PASSWORD "oper-01A"
END