In this mode, SPML Provider directly connects to the specified domain or AD LDS instance.
A set of optional, functionally related operations defined in SPML v2.
The minimum set of operations that a provider must implement to conform to the official SPML v2 specification.
A meta-markup language that provides a format for describing structured data. This facilitates more precise declarations of content and more meaningful search results across multiple platforms. In addition, XML enables a new generation of Web-based data viewing and manipulation applications.
An international consortium that drives the development, convergence, and adoption of e-business and Web service standards.
See Provisioning Service Provider.
Represents a data entity or an information object on a target.
A software component that listens for, processes, and returns the results for well-formed SPML requests from a known requestor.
Represents a destination or endpoint that a provider makes available for provisioning actions.
In proxy mode, SPML Provider accesses directory data using the Active Roles proxy service.
A software component that issues well-formed SPML requests to a Provisioning Service Provider.
See Requesting Authority.
An XML/HTTP-based protocol for platform-independent access to objects and services on the Web. SOAP defines a message format in XML that travels over the Internet using HyperText Transfer Protocol (HTTP). By using existing Web protocols (HTTP) and languages (XML), SOAP runs over the existing Internet infrastructure without being tied to any operating system, language, or object model.
An XML-based framework for exchanging user, resource, and service provisioning information between cooperating organizations.
An OASIS standard that provides a means of representing provisioning requests and responses as SPML documents.
See Provisioning Service Target.
Defines the XML structure of the objects (PSO) that the target may contain.
This section briefly discusses some error statements that you may encounter when using SPML Provider.
When sending a request to remove a user from a group (see the example below), the requested operation fails with the error statement “Cannot remove the specified item because it was not found in the specified Collection.”
This error has one of the following causes:
Verify that the <value> element specifies the distinguished name of the user that is the group member. Make sure that the Distinguished Name fields are in upper case.
The following example illustrates how to create a request to remove user Robert Smith from the Sales group.
<?xml version="1.0"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<modifyRequest xmlns="urn:oasis:names:tc:SPML:2:0" returnData="everything">
<psoID ID="CN=Sales,OU=SPML2,DC=Mycompany,DC=com"/>
<modification modificationMode="delete">
<data>
<attr name="member" xmlns="urn:oasis:names:tc:DSML:2:0:core">
<value>CN=Robert Smith,OU=Staff,DC=MyCompany,DC=com</value>
</attr>
</data>
</modification>
</modifyRequest>
</soap:Body>
</soap:Envelope>
When sending a request to change values of an object virtual attribute, the requested operation fails with the error statement “Some of the specified attributes for the '<object class name>' object class are not defined in the schema.”
This error has one of the following causes:
To resolve this issue, recycle the Default Application Pool or change its settings using Internet Information Services (IIS) Manager.
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책