The between-host user account mapping feature enables job submission and execution within a cluster that has different user accounts assigned to different hosts. Using this feature, you can map a local user account to a different user account on a remote host.
Local user account mapping—for UNIX or Windows hosts, a user can map the local user account to a different user on a remote host
Windows workgroup account mapping—allows LSF administrators to map all Windows workgroup users to a single Windows system account, eliminating the need to create multiple users and passwords in LSF. Users can submit and run jobs using their local user names and passwords, and LSF runs the jobs using the mapped system account name and password. With Windows workgroup account mapping, all users have the same permissions because all users map to the same Windows system account.
Users can map their local accounts at the user level in the file .lsfhosts. This file must reside in the user’s home directory with owner read-write permissions for UNIX and owner read-write-execute permissions for Windows. It must not be readable and writable by any other user other than the owner. Save the .lsfhosts file without a file extension. Both the remote and local hosts must have corresponding mappings in their respective .lsfhosts files.
LSF administrators can set up Windows workgroup account mapping at the system level in lsb.params.
The following example describes how local user account mapping works when configured in the file .lsfhosts in the user’s home directory. Only mappings configured in .lsfhosts on both the local and remote hosts work.