#include <errno.h>
#include <sys/param.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include "XrdSec/XrdSecEntity.hh"

Include dependency graph for XrdSecInterface.hh:

Classes
struct	XrdSecBuffer
	Generic structure to pass security information back and forth. More...

class	XrdSecProtocol

class	XrdSecService

Typedefs
typedef XrdSecBuffer	XrdSecCredentials

typedef XrdSecBuffer	XrdSecParameters

typedef XrdSecProtocol (	XrdSecGetProt_t )(const char , XrdNetAddrInfo &, XrdSecParameters &, XrdOucErrInfo )
	Typedef to simplify the encoding of methods returning XrdSecProtocol. More...

typedef XrdSecService (	XrdSecGetServ_t )(XrdSysLogger , const char )

Typedef Documentation

typedef XrdSecBuffer XrdSecCredentials

When the buffer is used for credentials, the start of the buffer always holds the credential protocol name (e.g., krb4) as a string. The client will get credentials and the size will be filled out so that the contents of buffer can be easily transmitted to the server.

typedef XrdSecProtocol*(* XrdSecGetProt_t)(const char *, XrdNetAddrInfo &, XrdSecParameters &, XrdOucErrInfo *)

Typedef to simplify the encoding of methods returning XrdSecProtocol.

Each specific protocol resides in a shared library named "libXrdSec<p>.so" where

is the protocol identifier (e.g., krb5, gsi, etc). The library contains a class derived from the XrdSecProtocol object. The library must also contain a three extern "C" functions: 1) XrdSecProtocol

Init() Called for one-time protocol ininitialization. 2) XrdSecProtocol

Object() Called for protocol object instantiation. 3) XrdSecProtocol

Object_ Inspected for the protocol object xrootd version number used in compilation; defined by the XrdVERSIONINFO macro (see later comments).Perform one-time initialization when the shared library containing the the protocol is loaded.

Parameters

who	contains 'c' when called on the client side and 's' when called on the server side.
parms	when who == 'c' (client) the pointer is null. when who == 's' (server) argument points to any parameters specified in the config file with the seclib directive. If no parameters were specified, the pointer may be null.
einfo	The error information object where error messages should be placed. Should einfo be null, messages should be written to stderr.

Returns: Success: The initial security token to be sent to the client during the login phase (i.e. authentication handshake). If no token need to be sent, a pointer to null string should be returned. Failure: A null pointer with einfo, if supplied, holding the reason for the failure.

Notes: 1) Function is called ince in single-thread mode and need not be thread-safe.

extern "C" char *XrdSecProtocol

Init (const char who, const char *parms, XrdOucErrInfo *einfo) {. . . .}Obtain an instance of a protocol object.

Parameters

who	contains 'c' when called on the client side and 's' when called on the server side.
host	The client's host name or the IP address as text. An IP may be supplied if the host address is not resolvable. Use endPoint to get the hostname only if it's actually needed.
endPoint	the XrdNetAddrInfo object describing the end-point. When who == 'c' this is the client, otherwise it is the server.
parms	when who == 'c' (client) points to the parms sent by the server upon the initial handshake (see Init() above). when who == 's' (server) is null.
einfo	The error information object where error messages should be placed. Should einfo be null, messages should be written to stderr.

Returns: Success: A pointer to the protocol object. Failure: A null pointer with einfo, if supplied, holding the reason for the failure.

Notes 1) Warning! The protocol must allow both 'c' and 's' calls within the same execution context. This occurs when a server acts like a client. 2) This function must be thread-safe. 3) Additionally, you should declare the xrootd version you used to compile your plug-in using XrdVERSIONINFO where <name> is the 1- to 15-character unquoted name of your plugin. This is a mandatory requirement!

Example:

#include "XrdVersion.hh"
XrdVERSIONINFO(XrdSecProtocol<p>Object,<name>);

extern "C" XrdSecProtocol *XrdSecProtocol<p>Object
                                      (const char              who,
                                       const char             *hostname,
                                             XrdnetAddrInfo   &endPoint,
                                       const char             *parms,
                                             XrdOucErrInfo    *einfo
                                      ) {. . .}

The following extern "C" functions provide protocol object management. That is, coordinating the use of the right authentication protocol between the client and server. The default implementation may be replaced via a plugin. Create a client security context and get a supported XrdSecProtocol object for one of the protocols suggested by the server and possibly based on the server's hostname or host address, as needed.

Parameters

hostname	The client's host name or the IP address as text. An IP may be supplied if the host address is not resolvable. Use endPoint to get the hostname only if it's actually needed.
endPoint	the XrdNetAddrInfo object describing the server end-point.
sectoken	The security token supplied by the server.
einfo	The structure to record any error messages. These are normally sent to the client. If einfo is a null pointer, the messages should be sent to standard error.

Returns: Success: Address of protocol object to be used for authentication. If cred was null, a host protocol object should be returned if so allowed. The object's delete method should be called to release the storage. Failure: Null, no protocol can be returned. The einfo parameter, if supplied, has the reason.

Notes: 1) There should be one protocol object per physical TCP/IP connections. 2) When the connection is closed, the protocol's Delete() method should be called to properly delete the object. 3) The method and the returned object should be MT-safe. 4) When replacing the default implementation with a plug-in the extern "C" function below must exist in your shared library. 5) Additionally, you should declare the xrootd version you used to compile your plug-in using XrdVERSIONINFO where <name> is the 1- to 15-character unquoted name of your plugin. This is a mandatory requirement!

typedef XrdSecService*(* XrdSecGetServ_t)(XrdSysLogger *, const char *)

typedef XrdSecBuffer XrdSecParameters

When the buffer is used for parameters, the contents must be interpreted in the context that it is used. For instance, the server will send the security configuration parameters on the initial login. The format differs from, say, the x.500 continuation paremeters that would be sent during PKI authentication via an "authmore" return status.

Classes

Typedefs

Typedef Documentation