.TH "globus_gsi_proxy" 3 "Tue Nov 8 2016" "Version 8.6" "globus_gsi_proxy_core" \" -*- nroff -*-
.ad l
.nh
.SH NAME
globus_gsi_proxy \- Globus GSI Proxy API
.SS "Modules"

.in +1c
.ti -1c
.RI "\fBActivation\fP"
.br
.ti -1c
.RI "\fBHandle Management\fP"
.br
.RI "Create/Destroy/Modify a GSI Proxy Handle\&. "
.ti -1c
.RI "\fBHandle Attributes\fP"
.br
.ti -1c
.RI "\fBProxy Operations\fP"
.br
.RI "Initiate a proxy operation\&. "
.ti -1c
.RI "\fBProxy Constants\fP"
.br
.in -1c
.SH "Detailed Description"
.PP 
The globus_gsi_proxy library is motivated by the desire to provide a abstraction layer for the proxy creation and delegation process\&. For background on this process please refer to the proxy certificate profile draft\&.
.PP
Any program that uses Globus GSI Proxy functions must include \fC'globus_gsi_proxy\&.h'\fP\&.
.PP
We envision the API being used in the following manner:
.PP
Delegator Delegatee  set desired cert info extension in the handle by using the handle set functions\&. \fBglobus_gsi_proxy_create_req()\fP \fBglobus_gsi_proxy_inquire_req()\fP modify cert info extension by using \fBhandle set/get/clear functions\&.\fP \fBglobus_gsi_proxy_sign_req()\fP \fBglobus_gsi_proxy_assemble_cred()\fP The API documentation is divided into the following sections
.IP "\(bu" 2
\fBActivation\fP
.IP "\(bu" 2
\fBHandle Management\fP
.IP "\(bu" 2
\fBHandle Attributes\fP
.IP "\(bu" 2
\fBProxy Operations\fP
.IP "\(bu" 2
\fBProxy Constants\fP 
.PP

.SH "Author"
.PP 
Generated automatically by Doxygen for globus_gsi_proxy_core from the source code\&.