#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:
Go to the source code of this file.
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. | |
typedef XrdSecService *(*) | XrdSecGetServ_t (XrdSysLogger *, const char *) |
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.
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.
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. |
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.