1Internal pluggable interfaces 2============================= 3 4Following are brief discussions of pluggable interfaces which have not 5yet been made public. These interfaces are functional, but the 6interfaces are likely to change in incompatible ways from release to 7release. In some cases, it may be necessary to copy header files from 8the krb5 source tree to use an internal interface. Use these with 9care, and expect to need to update your modules for each new release 10of MIT krb5. 11 12 13Kerberos database interface (KDB) 14--------------------------------- 15 16A KDB module implements a database back end for KDC principal and 17policy information, and can also control many aspects of KDC behavior. 18For a full description of the interface, see the header file 19``<kdb.h>``. 20 21The KDB pluggable interface is often referred to as the DAL (Database 22Access Layer). 23 24 25Authorization data interface (authdata) 26--------------------------------------- 27 28The authdata interface allows a module to provide (from the KDC) or 29consume (in application servers) authorization data of types beyond 30those handled by the core MIT krb5 code base. The interface is 31defined in the header file ``<krb5/authdata_plugin.h>``, which is not 32installed by the build. 33