Configuration to enable cross-cluster user account mapping

You can enable cross-cluster user account mapping at the system or user level. The enablement is completed in different configuration files, but different users, depending on the configuration level.

  • LSF administrators can map user accounts at the system level in the UserMap section of the lsb.users file. Both the remote and local clusters must have corresponding mappings in their respective lsb.users files.
  • Users can map their local accounts at the user level in the .lsfhosts file. 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. Save the .lsfhosts file without a file extension. Both the remote and local hosts must have corresponding mappings in their respective .lsfhosts files.
Restriction: Define either system-level or user-level mapping, but not both. LSF ignores system-level mapping if user-level mapping is also defined in .lsfhosts.
Configuration file Level Syntax Behavior
lsb.users System

Required fields: LOCAL, REMOTE, and DIRECTION
  • Maps a user name on a local host to a different user name on a remote host
  • Jobs that execute on a remote host run using a mapped user name rather than the job submission user name
.lsfhosts User host_name user_name send
  • Jobs sent from the local account run as user_name on host_name
host_name user_name recv
  • The local account can run jobs received from user_name submitted on host_name
host_name user_name
  • The local account can send jobs to and receive jobs from user_name on host_name
cluster_name user_name
  • The local account can send jobs to and receive jobs from user_name on any host in the cluster cluster_name

+ +
  • The local account can send jobs to and receive jobs from any user on any LSF hosts