The localUserId element in the job description is 
intended to support selecting a local account 
when the grid mapfile maps a DN to multiple 
local accounts. 

The WS-GRAM job execution service processes correctly this 
element, and it submits the job using basically 

 sudo -u localUserId  globus-gridmap-and-execute \
      -g /etc/grid-security/grid-mapfile               \
      globus-job-manager-script.pl ...



The above command is in the /etc/sudoers file to allow 
the user globus to sudo to localUserId

$GLOBUS_LOCATION/libexec/globus-gridmap-and-execute \
   -g /etc/grid-security/grid-mapfile               \
   $GLOBUS_LOCATION/libexec/globus-job-manager-script.pl *

This command checks that localUserId is in the map-file 
(the check is done, I believe in globus-gridmap-and-execute) 
and it fails if the localUserId is not the first entry in the 
list of local accounts.

Example:


(1) My DN is mapped to two local accounts:

   "/C=DE/O=GridGermany/OU=Leibniz-Rechenzentrum/OU=HLS/CN=Gabriel Mateescu"   
lrz015ab,a2815ab


(2) I submit a "whoami" job in which I indicate that 
    I want to use as localuserId the second account 
    in grid-mapfile, i.e., a2815ab


 $ more whoami.rsl
  <job>
      <localUserId>a2815ab</localUserId>
      <executable>/usr/bin/whoami</executable>
      <directory>/tmp</directory>
      <stdout>/tmp/gabriel.stdout</stdout>
      <stderr>/tmp/gabriel.stderr</stderr>
   </job>


 $ globusrun-ws -submit -F a01.hlrb2 -f whoami.rsl
  Submitting job...Done.
  Job ID: uuid:90e0788a-823a-11dc-95b0-0800691514bf
  Termination time: 10/25/2007 14:08 GMT
  Current job state: Failed
  Destroying job...Done.
  globusrun-ws: Job failed: Error code: 201
  Script stderr:
  a2815ab is not in the grid mapfile


(3) The error 


       a2815ab is not in the grid mapfile

    is the bug, because  a2815ab is in fact in the grid 
    mapfile. It is just not the first entry, but the 
    second.