HCL Workload Automation, Version 9.4

2. Update the HCL Workload Automation security file

You need to update the HCL Workload Automation security file to allow users to access HCL Workload Automation objects (for more detailed information, see Updating the security file). The following example shows an updated security file, where the user TEST_LDAP has been added to the USER MAESTRO section:
USER MAESTRO
	CPU=@+LOGON=tws83,Administrator,administrator,TEST_LDAP 
BEGIN
	USEROBJ	CPU=@		ACCESS=ADD,DELETE,DISPLAY,MODIFY,ALTPASS,UNLOCK,LIST
	JOB		CPU=@		ACCESS=ADD,ADDDEP,ALTPRI,CANCEL,CONFIRM,DELDEP,DELETE,DISPLAY,KILL,
              				MODIFY,RELEASE,REPLY,RERUN,SUBMIT,USE,LIST,UNLOCK
	SCHEDULE	CPU=@	ACCESS=ADD,ADDDEP,ALTPRI,CANCEL,DELDEP,DELETE,
								DISPLAY,LIMIT,MODIFY,RELEASE,REPLY,SUBMIT,LIST,UNLOCK
	RESOURCE	CPU=@	ACCESS=ADD,DELETE,DISPLAY,MODIFY,RESOURCE,USE,LIST,UNLOCK
	PROMPT				ACCESS=ADD,DELETE,DISPLAY,MODIFY,REPLY,USE,LIST,UNLOCK
	FILE		NAME=@	ACCESS=CLEAN,DELETE,DISPLAY,MODIFY,UNLOCK
	CPU		CPU=@		ACCESS=ADD,CONSOLE,DELETE,DISPLAY,FENCE,LIMIT,LINK,MODIFY,
								SHUTDOWN,START,STOP,UNLINK,LIST,UNLOCK
	PARAMETER	 CPU=@	ACCESS=ADD,DELETE,DISPLAY,MODIFY,UNLOCK,LIST
	CALENDAR				ACCESS=ADD,DELETE,DISPLAY,MODIFY,USE,UNLOCK,LIST
END
In this example, the useDomainQualifiedUserNames security property is set to false therefore the user name has been specified without the domain.