Re: Including custom X.509 extension upon proxy renewal

To: myproxy-users@ncsa.uiuc.edu
Subject: Re: Including custom X.509 extension upon proxy renewal
From: Christopher Kunz <kunz@rvs.uni-hannover.de>
Date: Tue, 12 Jun 2007 15:38:34 +0200
Content-transfer-encoding: 7bit
Content-type: text/plain; charset=ISO-8859-15
In-reply-to: <5312.1181311616@ncsa.uiuc.edu>
References: <4667F423.9030003@rvs.uni-hannover.de> <20070607121859.GA6608@acamara> <4667FAEC.5010506@rvs.uni-hannover.de> <5312.1181311616@ncsa.uiuc.edu>
Sender: owner-myproxy-users@ncsa.uiuc.edu
User-agent: Thunderbird 2.0.0.0 (Windows/20070326)

Jim Basney schrieb:

> Yes: ssl_proxy_delegation_init(), ssl_proxy_delegation_sign(), and
> ssl_proxy_delegation_finalize().

These operate on the request using the globus API functions. However, there
doesn't seem to be a function in globus_gsi_proxy.h or anywhere else in the
Globus API that adds a custom extension to a globus request handle.

Is there any way to convert the handle back to an X509_REQ and operate on that
from within ssl_proxy_delegation_sign?

Regards,

--ck

Follow-Ups:
- Re: Including custom X.509 extension upon proxy renewal
  - From: Jim Basney <jbasney@ncsa.uiuc.edu>

References:
- Including custom X.509 extension upon proxy renewal
  - From: Christopher Kunz <kunz@rvs.uni-hannover.de>
- Re: Including custom X.509 extension upon proxy renewal
  - From: Daniel Kouril <kouril@ics.muni.cz>
- Re: Including custom X.509 extension upon proxy renewal
  - From: Christopher Kunz <kunz@rvs.uni-hannover.de>
- Re: Including custom X.509 extension upon proxy renewal
  - From: Jim Basney <jbasney@ncsa.uiuc.edu>

Prev by Date: Re: Proxy Renewal: Receiving the second authentication credentials
Next by Date: Re: Including custom X.509 extension upon proxy renewal
Previous by thread: Re: Including custom X.509 extension upon proxy renewal
Next by thread: Re: Including custom X.509 extension upon proxy renewal

Other Mailing lists | Author Index | Date Index | Subject Index | Thread Index