Previous Topic: Change PagesNext Topic: Compiling & Linking


APS Application Programming Interface

Starting with Version 3.0, APS provides a true Application Programming Interface (API). This interface does not provide a generic interface to updating directories; rather, it provides programmatic access to APS' password evaluation capabilities and run-time authentication checking.

The API is "housed" in a library called APSAPI (under Windows, APSAPI.DLL, and under Solaris, libAPSAPI.so). This library and the required C/C++ language header file, are installed with APS on the Policy Server under the SDK directory.

The API is supplied for C/C++ and COM only. If it must be called from Java, it is up to the site to build a JNI interface to the API, though a JNI interface may be provided with a future release. It is not possible at this time to produce a native Java API, because the APS API calls into the SiteMinder Agent API, which is C/C++ only. Thus, a JNI call must be made at that point. The SiteMinder Agent API remains C/C++ only for security reasons.

CA Professional Services can be contracted to write programs that use this API and can be contracted to help architect applications that use it. However, we do not provide direct support for customer-written programs that use the API. Since APS includes utilities (such as SmCPW and APSAdmin) that call the API, the API itself can be tested cleanly without using customer code. Failures in customer code should be tested using a CA-supplied interface before calling for support.

This section contains the following topics:

Compiling & Linking

Run-Time Requirements

Function Descriptions