This topic describes the strong authentication package (SAP). In addition to the attribute types, attribute syntaxes, and object classes defined in the basic directory contents package, the standards also contain definitions to support authentication mechanisms. They include such objects as Strong-Authentication-User.
Note: These definitions are chiefly in The Directory: Selected Attribute Types (ISO 9594-6, CCITT X.520) and The Directory: Selected Object Classes (ISO 9594-7, CCITT X.521) with additional material in The Directory: Overview of Concepts, Models, and Services (ISO 9594-1, CCITT X.500) and The Directory: Authentication Framework (ISO 9594-8, CCITT X.509).
This topic outlines names for each of these items, and it defines OM classes to represent those that are not represented directly by OM syntaxes. The values of attributes in the directory are not restricted to those discussed in this topic, and new attribute types and syntaxes can be created at any time. (For further information on how the values of other syntaxes are represented in the interface, see XDS Interface Description.)
The constants and OM classes in this topic are defined in addition to those in XDS Class Definitions, since they are not essential to the working of the interface, but instead allow directory entries to be utilized. The definitions belong to the SAP, which is supported by the DCE XDS API following negotiation of its use with ds_version( ).
The object identifier associated with the SAP is
{iso(1) identified-organization(3) icd-ecma(0012) member-company(2)
dec(1011) xopen(28) sap(2)}\*O
It takes the following encoding:
\x2B\xC\x2\x87\x73\x1C\x2
This identifier is represented by the constant DS_STRONG_AUTHENT_PKG. The C constants associated with this package are in the xdssap.h header file.
The concepts and notation used are introduced in XDS Class Definitions. They are also fully explained in Information Syntaxes, XOM Service Interface , and Object Management Package.
The selected attribute types are presented first, followed by the selected object classes. Next, the OM class hierarchy and OM class definitions required to support the selected attribute types are presented.