<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugzilla.globus.org/bugzilla/bugzilla.dtd">

<bugzilla version="3.2.3"
          urlbase="http://bugzilla.globus.org/bugzilla/"
          maintainer="bacon@mcs.anl.gov"
>

    <bug>
          <bug_id>4021</bug_id>
          
          <creation_ts>2005-12-07 16:36</creation_ts>
          <short_desc>globus-start-container -containerDesc not working</short_desc>
          <delta_ts>2005-12-09 15:38:21</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Java WS Security</product>
          <component>Authentication</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          
          <priority>P3</priority>
          <bug_severity>critical</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Peter Lane">lane@mcs.anl.gov</reporter>
          <assigned_to name="Rachana Ananthakrishnan">ranantha@mcs.anl.gov</assigned_to>
          <cc>gawor@mcs.anl.gov</cc>
    
    <cc>meder@mcs.anl.gov</cc>

      

      
          <long_desc isprivate="0">
            <who name="Peter Lane">lane@mcs.anl.gov</who>
            <bug_when>2005-12-07 16:36:42</bug_when>
            <thetext>The -containerDesc option to globus-start-container doesn&apos;t seem to be working
in the trunk. When I specify the following security config file:

&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;containerSecurityConfig
xmlns=&quot;http://www.globus.org/security/descriptor/container&quot;
xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; 
xsi:schemaLocation=&quot;http://www.globus.org/security/descriptor
name_value_type.xsd&quot; xmlns:param=&quot;http://www.globus.org/security/descriptor&quot;&gt;
    &lt;defaultAuthzParam&gt;
        &lt;interceptor name=&quot;gridmap&quot;&gt;
            &lt;parameter&gt;
                &lt;param:nameValueParam&gt;
                    &lt;param:parameter name=&quot;gridmap-file&quot;
                                     value=&quot;&quot;/&gt;
                &lt;/param:nameValueParam&gt;
            &lt;/parameter&gt;
        &lt;/interceptor&gt;
    &lt;/defaultAuthzParam&gt;
&lt;/containerSecurityConfig&gt;

I expect that the container will run with my user creds, but when I try to
submit a job with globusrun-ws -self I get the following error:

GSS Major Status: Unexpected Gatekeeper or Service Name
globus_gsi_gssapi: Authorization denied: The name of the remote entity
(/C=US/O=PGL Inc./CN=host/logan), and the expected name for the remote entity
(/DC=org/DC=doegrids/OU=People/CN=Peter G Lane 364243) do not match

Thinking that the file was being ignored in favor of
$GLOBUS_LOCATION/etc/globus_wsrf_core/globus_security_descriptor.xml, I
commented out the &lt;credential&gt; stuff so that it would look like the above
descriptor. Unfortunately I get an even stranger error:

GSS Major Status: General failure
globus_gsi_gssapi: internal problem with SSL BIO: SSL_read rc=-1
OpenSSL Error: pem_lib.c:637: in library: PEM routines, function PEM_read_bio:
no start line Expecting: CERTIFICATE</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Rachana Ananthakrishnan">ranantha@mcs.anl.gov</who>
            <bug_when>2005-12-09 15:38:21</bug_when>
            <thetext>The command line option descriptor has been fixed. The second issue 
with &quot;authorization denied&quot; has been moved to a separate bug.</thetext>
          </long_desc>
      
      

    </bug>

</bugzilla>