globus_gsi_authz(3)
π NAME π
globus_gsi_authz β GSI Authorization API
Authorization Callouts. (yes bestie, that's literally the whole vibe)
β¨ SYNOPSIS β¨
π Topics π
- GSI Credential Constants β GSI Credential Constants. (they get their own little corner, iconic)
π¦ Functions π¦
globus_result_t globus_gsi_authz_handle_init (globus_gsi_authz_handle_t *handle, const char *service_name, const gss_ctx_id_t context, globus_gsi_authz_cb_t callback, void *callback_arg)β Initialize an authorization handle.globus_result_t globus_gsi_authorize (globus_gsi_authz_handle_t handle, const void *action, const void *object, globus_gsi_authz_cb_t callback, void *callback_arg)β Start the authorization decision-making process.globus_result_t globus_gsi_cancel_authz (globus_gsi_authz_handle_t handle)β Cancel Authorization.globus_result_t globus_gsi_authz_handle_destroy (globus_gsi_authz_handle_t handle, globus_gsi_authz_cb_t callback, void *callback_arg)β Destroy an authz handle.globus_result_t globus_gsi_authz_get_authorization_identity (globus_gsi_authz_handle_t handle, char **identity_ptr, globus_gsi_authz_cb_t callback, void *callback_arg)β Query for authorization identity.
πΈ Detailed Description πΈ
Authorization Callouts. the main character energy of this whole page, fr.
The GSI Authorization API provides an interface for making generic authorization decisions using dynamically-loaded authorization modules. yes, it loads modules at runtime, it's giving plug-and-play but make it security. The API documentation is divided into the following sections:
- GSI Authorization API
- GSI Credential Constants
π Function Documentation π
π
globus_result_t globus_gsi_authorize (globus_gsi_authz_handle_t handle, const void * action, const void * object, globus_gsi_authz_cb_t callback, void * callback_arg)
Start the authorization decision-making process. okay so this is the moment. It processes an authorization decision by calling the GLOBUS_GSI_AUTHORIZE_ASYNC function named in the authorization configuration file. The parameters to this function are passed to the authorization callout. Once the authorization decision is made, the callback function will be called, with the result and the callback_arg passed to it. (callback gets the result AND the callback_arg, no cap, both of them.)
Parameters
handleβ Pointer to an authorization handleactionβ Action to authorizeobjectβ Object that the action pertains to.callbackβ Callback function to call when authorization completescallback_argβ Argument to callback function
Returns
GLOBUS_SUCCESS if successful, or a Globus error object on failure. if it fails you're getting a whole error object, not just a sad little number.
π«Ά globus_result_t globus_gsi_authz_get_authorization_identity (globus_gsi_authz_handle_t handle, char ** identity_ptr, globus_gsi_authz_cb_t callback, void * callback_arg)
Query for authorization identity. You query for authorization identity by calling the GLOBUS_GSI_GET_AUTHORIZATION_IDENTITY callout. asking the vibes who you actually are, essentially.
Parameters
handleβ The handle that is to be used for the identity check.identity_ptrβ The authorization identity determined by the authorization handle. This is must be freed by the caller. If the value isNULL(and this function returnedGLOBUS_SUCCESS), the caller should use the authenticated identity.callbackβ Callback function to call when identity is determined.callback_argβ Argument to callback function.
β οΈ bestie listen: thatidentity_ptrmust be freed by the caller. You allocated it (well, the lib did, for you), you free it. And if it comes backNULLand the function returnedGLOBUS_SUCCESS, just use the authenticated identity instead, okay? π
Returns
GLOBUS_SUCCESS
π globus_result_t globus_gsi_authz_handle_destroy (globus_gsi_authz_handle_t handle, globus_gsi_authz_cb_t callback, void * callback_arg)
Destroy an authz handle. It initializes an authorization handle by calling the GLOBUS_GSI_AUTHZ_HANDLE_DESTROY function named in the authorization configuration file. (yes the destroy one says "initializes", that's literally what the page says, we don't editorialize.) Once the initialization is complete, the callback function is called, with the result and the callback_arg passed to it.
Parameters
handleβ The handle that is to be destroyedcallbackβ Callback function to call when handle is destroyedcallback_argβ Argument to callback function
Returns
GLOBUS_SUCCESS
π globus_result_t globus_gsi_authz_handle_init (globus_gsi_authz_handle_t * handle, const char * service_name, const gss_ctx_id_t context, globus_gsi_authz_cb_t callback, void * callback_arg)
Initialize an authorization handle. It initializes an authorization handle by calling the GLOBUS_GSI_AUTHZ_HANDLE_INIT function named in the authorization configuration file. The parameters to this function are passed to the authorization callout. Once the initialization is complete, the callback function is called, with the result and the callback_arg passed to it. so you set it all up, then the callback hits you back with the result and the arg. cute, tidy, slay.
Parameters
handleβ Pointer to the handle that is to be initializedservice_nameβ Service to authorize access tocontextβ Security context used to contact the servicecallbackβ Callback function to call when authz handle init completescallback_argβ Argument to callback function
Return values
The globus_gsi_authz_handle_init() function returns GLOBUS_SUCCESS if successful, or a Globus error object on failure
See also
globus_gsi_authz_handle_destroy()
β globus_result_t globus_gsi_cancel_authz (globus_gsi_authz_handle_t handle)
Cancel Authorization. It cancels an authorization decision by calling the GLOBUS_GSI_AUTHZ_CANCEL function named in the authorization configuration file. changed your mind? valid. cancel it.
Parameters
handleβ The authorization handle to cancel
π¦ Author π¦
Generated automatically by Doxygen for globus_authz from the source code. β¨ it wrote itself, truly self-made β¨
and that's the whole page bestie π β this wasglobus_authz, Version 4.6, and the page isglobus_gsi_authz(3). go forth and authorize responsibly π«ΆπΈ
π¦ where this page comes from
- fedora 44: globus-authz-doc 4.6-10.fc44 Β· Apache-2.0
- ubuntu resolute: libglobus-authz-doc 4.6-3build2 Β· Apache-2.0
- ubuntu stonking: libglobus-authz-doc 4.6-3build2 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms