SOAP
This connectivity package provides support for SOAP-based systems. The SOAP connector is available in a default installation.
Supported objects and operations
Both full import and delta import modes are available. Delta import is generally supported for most SOAP-based systems. The actual functionality implementation depends on how the registered system utilizes the delta import.
Identity data
| System objects | Omada Identity Data Model | Operations |
|---|---|---|
| Identities | - | Read |
| Contexts | - | Read |
| Identity Owner | - | Read |
| Context Owner | - | Read |
| Context Assignment | - | Read |
Access rights
| System objects | Omada Identity Data Model | Operations |
|---|---|---|
| Account | - | Read |
| Resource | - | Read |
| Resource Owner | - | Read |
| Resource Assignment | - | Read |
| Resource Parent/Child | - | Read |
Minimum required permissions
None.
Implementation notes
In the current release, SOAP connectivity is provided as a Technology Preview feature only. Technology Preview features may not be fully functional in the configuration that has been provided out of the box, so they should not be used in production environments without proper testing.
The SOAP collector allows you to:
- Load data from a system that uses SOAP via HTTP(S).
- Specify a custom request via a defined template in XML.
- Specify XPaths for mappings in the form of text.
- Read response data through XPath.
- Specify security protocols.
- Use basic authentication protocols or authentication services.
- Select a paging mechanism.
For both SOAP collector and connector it is possible to provide SOAPAction header.
Network requirements
None.
Prerequisites
To achieve connectivity, you need the endpoint address URL of the SOAP service to which the connection will be made. You need to have access to a SOAP user account registered in the service (endpoint address).
SOAP connector enables provisioning of data to any system that uses SOAP to communicate. Using this connector, it is possible to change any kind of data supported by Omada Identity to any SOAP-based system via HTTP(S). In order to modify information to XML, the connector uses XPath 1.1 technology. Familiarity with XML Path Language (XPath) is required for connector configuration. See the description of the XPath standard on the World Wide Web Consortium (W3C) website.