|
Create a GSS Name structure from the given hostname. This function tries to resolve the given host name string to the canonical DNS name for the host.
|
|
This routine accepts a GSSAPI security context and is called by the gram_gatekeeper. It isolates the GSSAPI from the rest of the gram code. Initialize a gssapi security connection. Used by the server. The context_handle is returned, and there is one for each connection. This routine will take cake of the looping and token processing, using the supplied get_token and send_token routines.
|
|
This is a asynchronous version of the globus_gss_assist_accept_sec_context() function. Instead of looping itself it passes in and out the read and written buffers and the calling application is responsible for doing the I/O directly.
Other gss errors on failure. |
|
Called once at the start of the process, to obtain the credentials the process is running under. The
|
|
Called once at the start of the process, to obtain the credentials the process is running under. All the parameters of the gss_acquire_cred, except the desired_name is a string of the form: [type:]name. This will be imported with the type.
|
|
Display the messages for the major and minor status on the file pointed at by fp. Takes care of the overloaded major_status if there was a problem with the get_token or send_token routines.
|
|
Display the messages for the major and minor status and return a string with the messages. Takes care of the overloaded major_status if there was a problem with the get_token or send_token routines.
|
|
Routines callable from globus based code to map a globusID to a local unix user. GRIDMAP environment variable pointing at the map file. Defaults to ~/.gridmap A gridmap file is required if being run as root. if being run as a user,it is not required, and defaults to the current user who is running the command. This is the same file used by the gssapi_cleartext but will be used with other gssapi implementations which do not use the gridmap file.
|
|
Check to see if a particular globusid is authorized to access the given local user account.
|
|
Routine for returning the default globus ID associated with a local user name. This is somewhat of a hack since there is not a guarenteed one-to-one mapping. What we do is look for the first entry in the gridmap file that has the local user as the default login. If the user is not a default on any entry, we find the first entry in which the user exists as a secondary mapping.
|
|
Import the security context from a file.
|
|
Initialize a gssapi security connection. Used by the client. The context_handle is returned, and there is one for each connection. This routine will take cake of the looping and token processing, using the supplied get_token and send_token routines.
|
|
This is a asynchronous version of the globus_gss_assist_init_sec_context() function. Instead of looping itself it passes in and out the read and written buffers and the calling application is responsible for doing the I/O directly.
Other gss errors on failure. |
|
Sets the context to handle restrictions.
|
|
Gets a token using the specific tokenizing functions, and performs the GSS unwrap of that token.
|
|
|
about globus |
globus toolkit |
dev.globus
Comments? webmaster@globus.org