Understanding the SPML Configuration

The sample SPML configuration uses SPML 1.0 and binds with SOAP 1.1 using HTTP or HTTPS 1.1 as the transport. All data transformation and processing is done in policies and style sheets.

The sample SPML import file does the following:

• Provides generic SPML functionality.

  The import file doesn't pair with a specific SPML application.

• Provides XDS-to-SPML and SPML-to-XDS conversions in policies.
• Handles Users, Groups, and Organizational Units

  Other objects can be handled through policy and style sheet customization.

• Handles a single value per attribute.

  Multiple values for an attribute can be handled through policy and style sheet customization.

• Handles a subset of the query operations.

  The configuration handles all queries as SPML scope = "subtree" and uses the entry and subordinate scope concepts. Specific query operations can be handled through policy and style sheet customization.

• Supports string, structured and Distinguished Name (DN) attribute types.
• Supports password set operation.

  Password synchronization might be possible through policy and style sheet customization.

• Handles the single (non-batch) operations of execution=synchronous and processing=sequential.

  Batch requests can be supported through policy and style sheet customization.

• Doesn't handle <addResponse><attributes> or <modifyResponse><modifications>.
• The Subscriber channel uses the application-returned Identifier value for the association key.
• The Publisher channel uses the DN for the association key and returns the association key as the Identifier value.