How to Use the authSDK

To implement authSDK in your installation, follow these steps:

Link the authSDK to your code.

To integrate the authSDK
into your existing code, include the expapi.h header file in the
calling code and link with the DLL or shared-object. On some platforms you might also
be required to link with other system libraries the authSDK requires.

This function generates a session handle for the user and client IP address.
It returns a string, in a buffer you allocate, containing a login URL to be used when
connecting to Calendar Server. The string is a kind of token providing proof of identity.
It is given to the client in the form of a cookie, or URL, inside HTTP headers or JavaScript.TM The client then connects to Calendar Server, presenting the
token as proof of identity.

Call this function to shutdown and cleanup any resources used by the authSDK.
It is not necessary to call this function in some environments (a simple login, for
example), but plug-ins using the API might want to reclaim resources and continue
running.

Other Tips

The following is a list of other things that must be done to assure success
in using the AuthSDK:

The value of service.http.allowadminproxy in the ics.conf file must be “yes”.

The parameter caladmin, passed in the init method, must have the same value as service.admin.calmaster.userid in the ics.conf file.

The parameter calpass, passed in the init method, must have the same value as service.admin.calmaster.cred in the ics.conf file.

The two parameters caladmin and calpass must be defined in your directory service.

If your calendar server is not listening on the default port 80, you
must use the SetHttpPort method with the correct port value.