Developers

• Converting Applications from v1 to v2
  • Tips for both clients and servers
  • Tips for clients
  • Tips for Servers
• Application Programmer’s Guide
  • Introduction
    • About this Guide
    • What is SASL?
  • Background
    • How did the world work before SASL?
    • SASL to the rescue!
  • Briefly
    • What is the Cyrus SASL library good for?
    • What does the Cyrus SASL library do?
    • What doesn’t the Cyrus SASL library do?
  • Client-only Section
    • A typical interaction from the client’s perspective
    • How does this look in code
  • Server-only Section
    • A typical interaction from the server’s perspective
    • How does this look in code?
  • Common Section
    • Callbacks and Interactions
    • Security layers
  • Example applications that come with the Cyrus SASL library
    • sample-client and sample-server
    • Cyrus imapd v2.1.0 or later
    • imtest, from Cyrus 2.1.0 or later
  • Miscellaneous Information
    • Empty exchanges
    • Idle
• Plugin Programmer’s Guide
  • Introduction
    • About this Guide
    • What is SASL?
  • Common Section
    • Overview of Plugin Programming
    • Use of sasl_utils_t
    • Error Reporting
    • Memory Allocation
    • Client Send First / Server Send Last
  • Client Plugins
  • Server Plugins
  • User Canonicalization (canon_user) Plugins
  • Auxiliary Property (auxprop) Plugins
• Testing
  • Testing the CMU SASL Library with the included sample applications
    • Example
  • Running the Testsuite application