resetPassword - Enables a requestor to change (to an unspecified value) the password for an object and to obtain that newly generated password value.
validatePassword - Enables a requestor to determine whether a specified value would be valid as the password for a specified object.
Reference capability
Search capability
search - The search operation obtains every object that matches a specified query.
iterate - The iterate operation obtains the next set of objects from the result set that the provider selected for a search operation.
closeIterator - The closeIterator operation tells the provider that the requestor has no further need for the search result that a specific <iterator> represents.
Suspend capability
suspend - The suspend operation enables a requestor to disable an object.
resume - The resume operation enables a requestor to re-enable an object that has been suspended.
active - The active operation enables a requestor to determine whether a specified object has been suspended.
Updates capability
updates - The updates operation obtains records of changes to objects.
iterate - The iterate operation obtains the next set of objects from the result set that the provider selected for an updates operation.
closeIterator - The closeIterator operation tells the provider that the requestor has no further need for the updates result set that a specific <iterator> represents.
Custom capabilities
An individual provider (or any third party) can define a custom capability that integrates with SPMLv2.
Features
Provisioning Service Object (PSO)
The key identifier in SPML is a PSO.
A Provisioning Service Object (PSO), sometimes simply called an object, represents a data entity or an information object on a target. For example, a provider would represent as an object each account that the provider manages.
Every object is contained by exactly one target. Each object has a unique identifier (PSO-ID).
Profile
SPMLv2 defines two “profiles” in which a requestor and provider may exchange SPML protocol:
XML Schema as defined in the “SPMLv2 XSD Profile” [SPMLv2-Profile-XSD].
DSMLv2 as defined in the “SPMLv2 DSMLv2 Profile” [SPMLv2-Profile-DSML].
A requestor and a provider may exchange SPML protocol in any profile to which they agree.
The DSMLv2 Profile may be more convenient for applications that access mainly targets that are LDAP or X500 directory services. The XSD Profile may be more convenient for applications that access mainly targets that are web services.