Hmm, looks ok. The only reason I can see is that at some point another grid-mapfile is being used than /etc/grid-security/grid-mapfile. Please enable debug logging on the server-side in ws-gram and send the container logfile containing logs of a problematic job submission.
Martin Marco Lackovic wrote: > On Tue, Jun 22, 2010 at 2:50 PM, Martin Feller <[email protected]> wrote: >> $GLOBUS_LOCATION/etc/globus_wsrf_core/global_security_descriptor.xml, > > <?xml version="1.0" encoding="UTF-8"?> > <securityConfig xmlns="http://www.globus.org";> > <credential> > <key-file value="/etc/grid-security/containerkey.pem"/> > <cert-file value="/etc/grid-security/containercert.pem"/> > </credential> > <gridmap value="/etc/grid-security/grid-mapfile"/> > </securityConfig> > > >> $GLOBUS_LOCATION/etc/gram-service/managed-job-factory-security-config.xml, > > <securityConfig xmlns="http://www.globus.org";> > <method name="createManagedJob"> > <auth-method> > <GSITransport/> > <GSISecureMessage/> > <GSISecureConversation/> > </auth-method> > </method> > <authz value="gridmap"/> > <reject-limited-proxy value="true"/> > </securityConfig> > > >> $GLOBUS_LOCATION/etc/gram-service/managed-job-security-config.xml > > <securityConfig xmlns="http://www.globus.org";> > <auth-method> > <GSITransport/> > <GSISecureMessage/> > <GSISecureConversation/> > </auth-method> > <authz value="gridmap"/> > <run-as> <resource-identity/> </run-as> > </securityConfig> > > >> Um, but I see that you didn't run 'make install' after configure and make, >> which is a required step. >> What if you run 'make install' at the end and try it then? > > Sorry, I forgot to mention that but I actually already did that too. > >
