Configuring SOAP Accounts

Owned by Amritesh Singh
Last updated: Aug 22, 2024 by Rachana Mannath
4 min read

This account is used by the Snaps in the SOAP Snap Pack.

To create accounts in SnapLogic Manager, you need the File-Write permission on Accounts. To use the Account within Snaps in Designer, you need the File-Read permission on Accounts.

You can create an account from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:

  • Your private project folder: This folder contains the pipelines that will use the account.
  • Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
  • The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.


Account Configuration

In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for SOAP: 

  1. Click Create, then select SOAP, then either SOAP account.
  2. Supply an account label.
  3. Supply the Username and Password for you SOAP account.
  4. (Optional) Supply additional information on this account in the Notes field of the Info tab.
  5. Click Apply.


Account Types

SOAP Basic Auth

 Account Settings


Label

Required. User provided label for the account instance.

Username


Required. The name for this account.

Default value: [None]

Password


Required. The password for the account.

Default value: [None]

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

  • High: Password
  • Medium + High: Username, password
  • Low + Medium + High: Username, password

SOAP NTLM Account

 Account Settings


Label

Required. User provided label for the account instance.

Username


Required. The name for this account.

Default value: [None]

Password


Required. The password for the account.

Default value: [None]

Domain

The NTLM domain for the account.

Default value: [None]

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

  • High: Password
  • Medium + High: Username, password
  • Low + Medium + High: Username, password

SOAP SSL Account

 Account Settings


Label

Required. User provided label for the account instance

Username


The name for this account.

Default value: [None]

Password


The password for the account.

Default value: [None]

KeyStore


The location of the key store file, can be in SLDB or any other unauthenticated endpoint such as https://...
Default value: [None]

TrustStore


The location of the trust store file, can be in SLDB or any other unauthenticated endpoint such as https://...

Default value: [None]

Key/Trust store password


Password for the key/trust store. It is used for both if both are defined.

Default value: [None]

Key alias


Lets you define the key being used by its alias.

Default value: [None]

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

  • High: Password
  • Medium + High: Password, Key/Trust store password
  • Low + Medium + High: Password, Key/Trust store password

SOAP WSSE Account

 Account Settings


Label

Required. User provided label for the account instance.

Username


The name for this account.

Default value: [None]

Password


The password for the account.

Default value: [None]

Username Token Id

The value of Id attribute for the Username Token element.

Default value: [None]

Must Understand

The checkbox to include value of Must Understand for the Security Token.

Default value: [Unchecked]

WS-Security Version

The version of the WS-Security specification to follow.

Default value: WS-Security 1.0

Account Encryption

Standard Encryption

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

Enhanced Encryption

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account:

  • High:
  • Medium + High:
  • Low + Medium + High: 

The WSSE account for SOAP authentication enables the user to replace the security element from the SOAP header. All the necessary elements required for header must be included manually in the custom template. (The custom template does not generate it).

For example, if the original request looks like:

<SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:ns0="urn:messages.ws.rightnow.com/v1_2">
    <SOAP-ENV:Header>
        <h:ClientInfoHeader
            xmlns:h="urn:messages.ws.rightnow.com/v1_2"
            xmlns="urn:messages.ws.rightnow.com/v1_2"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xmlns:xsd="http://www.w3.org/2001/XMLSchema">
            <AppID>Contact Search</AppID>
        </h:ClientInfoHeader>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
      .....
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

After adding the WSSE account, the request would be:

<SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:ns0="urn:messages.ws.rightnow.com/v1_2">
    <SOAP-ENV:Header>
        <h:ClientInfoHeader
            xmlns:h="urn:messages.ws.rightnow.com/v1_2"
            xmlns="urn:messages.ws.rightnow.com/v1_2"
            xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xmlns:xsd="http://www.w3.org/2001/XMLSchema">
            <AppID>Contact Search</AppID>
        </h:ClientInfoHeader>
        <o:Security s:mustUnderstand="1"
            xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
            <o:UsernameToken>
                <o:Username>XXXXXX</o:Username>
                <o:Password>XXXXXXXXXX</o:Password>
            </o:UsernameToken>
        </o:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
      .....
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The security header would automatically be created from the account and added to the SOAP header. 

Snap Pack History

 Click to view/expand
ReleaseSnap Pack VersionDateTypeUpdates
August 2024438patches28073 Latest

Fixed an issue with the SOAP Execute Snap, where the Snap could not identify the '@' character after the Velocity library upgrade, implemented as part of the August 2024 GA release (main27765).

August 2024main27765

 

StableUpdated and certified against the current SnapLogic Platform release.

May 2024

main26341

 

Stable

Updated and certified against the current SnapLogic Platform release.

February 2024main25112 StableUpdated and certified against the current SnapLogic Platform release.
November 2023main23721 StableUpdated and certified against the current SnapLogic Platform release.
August 2023434patches22655 Latest

Fixed an issue with the SOAP Execute Snap that caused it to be unable to parse some WSDL files.

August 2023

main22460

 

Stable

Updated and certified against the current SnapLogic Platform release.

May 2023main21015 StableUpgraded with the latest SnapLogic Platform release.
February 2023432patches20553 Latest

  • Fixed the storage issue with the JCC output file caused by the cyclic import of WSDL warning logs by SOAP Snaps.

  • The performance of the SOAP Execute Snap has been enhanced by reducing the need for multiple WSDL downloads and parsing to obtain the same Description.

February 2023main19844 StableUpgraded with the latest SnapLogic Platform release.
November 2022main18944 StableUpgraded with the latest SnapLogic Platform release.
September 2022430patches18332 Latest

The SOAP Execute Snap now does not display the null pointer exception when parsing the given WSDL to generate the Customize Envelope.

August 2022430patches17325 Latest
  • The patch 429patches17186, previously deployed for the SOAP Execute Snap caused an error (the failure of the getOrderStatus operation) even when the WSDL is valid. With the latest patch, this Snap generates the customized envelope without errors when you upload a valid WSDL

  • The SOAP Execute Snap does not throw a Null Pointer Exception when using the Import Schema http://schemas.xmlsoap.org/soap/encoding/'.

August 2022main17386 StableUpgraded with the latest SnapLogic Platform release.
4.29 Patch429patches17186 LatestFixed an issue with the SOAP Execute Snap where the Snap displayed an error when a valid WSDL getOrderStatus SOAP operation was uploaded.

4.29

main15993

 

Stable

Upgraded with the latest SnapLogic Platform release.

4.28main14627 StableUpgraded with the latest SnapLogic Platform release.

4.27

main12833

 

Stable

Upgraded with the latest SnapLogic Platform release.
4.26main11181
 
StableUpgraded with the latest SnapLogic Platform release.
4.25 Patch425patches10994
 
Latest

Enhanced the SOAP Snap Pack to support HTTP Proxy Authentication.

4.25 Patch425patches10152
 
Latest

Enhanced the SOAP Execute Snap with a new checkbox Escape special characters that enable the snap to escape XML special characters in XML template variable values when this Snap inserts these values into the Apache Velocity template.

4.25main9554
 
StableUpgraded with the latest SnapLogic Platform release.
4.24 Patch424patches9077
 
Latest
  • Fixes the incremental thread count issue in the SOAP Execute Snap by ensuring that only instance of SoapCustomAsyncHTTPConduitFactory should pass throughout the execution of the Snap.
  • Fixes the issue in SOAP Execute Snap where the Snap failed as the default value of Content-Type field had been modified after upgrading the Snap in 4.24 release.
4.24main8556
 
StableUpgraded with the latest SnapLogic Platform release.
4.23 Patch423patches7411-Latest

Enhances the SOAP Execute Snap by including an additional output view. When named debug (all lower-case), the Snap outputs the SOAP request headers, envelope, and the output document that is written to the default output view. 

4.23main7430
 
Stable

Upgraded with the latest SnapLogic Platform release.

4.22 Patch422patches6770
 
Latest

Enhances the SOAP Execute Snap by adding WSSE header to support SOAP WSSE Account with Apache HttpComponents library.

4.22 Patch422patches6656
 
Latest

Fixes the SOAP Execute Snap failure due to different character sets used in the HTTP request data.

4.22main6403
 
StableUpgraded with the latest SnapLogic Platform release.
4.21 Patch421patches6040
 
Latest

Requires the use of a generic envelope while executing a create a request through an NTLM account in the SOAP Execute Snap to ensure the output is rendered as expected.

4.21snapsmrc542-Latest

Enhances SOAP Execute, by making it necessary to provide both key and value under the HTTP header field while invoking a task.

4.20 Patchsoap8816
Latest

Enhances the SOAP Execute Snap to allow user-specified empty fields in the SOAP request.

4.20 Patchsoap8762
 
Latest
  • Fixes the SOAP Execute Snap to:
    • Successfully handle redirected requests, when the WSDL file specifies an HTTP URL which redirects SOAP requests to an HTTPS URL.
    • Successfully generate the schema even if the XSD does not contain the <types> element.  
4.20 Patchsoap8712
Latest

Fixes the SOAP Execute Snap where the Snap throws an NPE error when generating a SOAP request template.

4.20snapsmrc535-StableUpgraded with the latest SnapLogic Platform release.
4.19 Patchsoap8642-Latest
  • Fixes the SOAP Execute Snap where the Snap encounters the following issues:
    • The Snap throws NPE when generating a SOAP request template.
    • The Snap throws the following error when making a SOAP call, if the SOAPAction HTTP header contains a string: Does not match an operation.
4.19 Patchsoap8375-Latest

The SOAP Snaps have a Library API field. When the selected value is the non-default HTTP Components, there was a breaking change in the structure of the output response document between 4.19 GA version (snapsmrc528) and the latest patch version (soap8375). We recommend that if you want to use the non-default (non-CXF) value for Library API, then you must use this latest patch version as subsequent GA releases may result in Pipeline executions failing. 

If your current or new Pipelines use CXF as the Library API value, or do not handle SOAP response bodies greater than 1000 lines, or do not rely on NTLM authentication, then you can continue using your existing Snap Pack version (stable distribution – snapsmrc528).

4.19snaprsmrc528-Stable

Adds the Library API field to the SOAP Execute Snap to enable execution over HTTP. The supported libraries are Apache HttpComponents and Apache CXF, and both the libraries support the Message Transmission Optimization Mechanism (MTOM).

4.18snapsmrc523-StableUpgraded with the latest SnapLogic Platform release.
4.17 PatchALL7402-Latest

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

4.17snapsmrc515-Stable

Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during the preview check box.

4.16 Patchsoap6886-Latest

Fixed an issue with the SOAP Execute Snap wherein SLDB protocols were not being supported.

4.16 snapsmrc508-StableUpgraded with the latest SnapLogic Platform release.
4.15 Patchsoap6726-Latest

Fixed an issue with the Soap Execute Snap failing for Workday when the Trust All certificate is enabled while using SSL authentication.

4.15 Patchsoap6699-Latest

Fixed an issue with the SOAP Execute Snap wherein errors where not getting routed to the error view and pipeline execution was failing.

4.15 Patchsoap6269-Latest

Removed synchronization from a WSDL service of SOAP Execute Snap to avoid hangs.

4.15 Patchsnapsmrc500-StableUpgraded with the latest SnapLogic Platform release.

4.14 Patch

soap6027-Latest

Removed the hardcoded timeout in ClientBuilder.

4.14 snapsmrc490-StableUpgraded with the latest SnapLogic Platform release.
4.13 Patchsoap5214-Latest

Fixed a bug in the SOAP Execute Snap wherein the end tag is removed incorrectly when generating the envelope.

4.12 Patchsoap5064-Latest
  • Fixed an issue with the SOAP Execute Snap that is unable to parse the XML schema information from the given WSDL.
4.12 Patchsoap4899-Latest

  • Fixed an issue with the SOAP Execute Snap, which hangs a pipeline at that Snap.

  • Added a new property in SOAP Execute "Include root element" that when enabled, provides the target schema. 

4.12 Patchsoap4821-Latest

Fixed a null pointer exception that displays while generating the SOAP templates.

4.12snapsmrc480-Stable

Added the property Exception To Error View to the SOAP Execute Snap to route the Snap exceptions to the error view.

4.11 Patchsoap4648-Latest

The SOAP Execute Snap now handles the WSDL child elements referencing the root schema element when generating envelope templates.

4.11snapsmrc465-Stable

Updated support of NTLM Account Authentication to SOAP Snap Pack.

4.10 Patchsoap3964-Latest

Fixed an issue with the Soap Execute Snap that fails with error "Failure:Error:Unable to parse XML schema information from the given WSDL"

4.10snapsmrc414-StableUpgraded with the latest SnapLogic Platform release.
4.9.0 Patchsoap3113-Latest

Addressed the issue: Error: Could not find the schema component' while generating custom envelope

4.9.0 Patchsoap3090-Latest

Addressed an NPE on Envelope generation in SOAP Execute Snap.

4.9snapsmrc405-StableUpgraded with the latest SnapLogic Platform release.
4.8.0 Patchsoap2966-Latest

Addressed an issue where Soap Execute Snap was unable to parse WSDL from CapGemini

4.8.0 Patchsoap2783-Latest

Addressed an issue with SOAP Execute Snap throwing an HTTP Response '404: Not found' error.

4.8.0 Patchsoap2719-Latest

Added the WS Addressing property to the SOAP Execute Snap.

4.8.0 Patchsoap2699-Latest

Removed the null values from the header during configure phase.

4.8.0 Patchsoap2703-Latest

Fixed performance issue on SOAP Snap Pack which was caused by the WSDL imports.

4.8.0snapsmrc398-Stable
  • Added support in the SOAP Snaps for WSDLs with import elements.
  • Added the Info tab to accounts.
4.7.0 Patchsoap2522-Latest

Addressed an 'Error: Could not translate an element declaration element' during envelope generation issue in the SOAP Execute Snap

4.7.0 Patchsoap2251-Latest

Addressed error while getting instance of Description for complex WSDLs.

4.7.0 Patchsoap2215-Latest

Support multiple namespaces in WSDLs.

4.7.0snapsmrc382-Latest

Updated the SOAP Execute Snap with a new property, Standardize error output.

4.6.0 Patchsoap2123-Latest

Resolved an issue where importing xsd files over https did not use proper authorization.

4.6.0 Patchsoap2064-Latest

A Gzip Interceptor was added to the SOAP client to uncompress Gzipped responses.

4.6.0 Patchsoap1932-Latest

Implemented a new property "Standardize error output " for the backward-compatibility.

4.6.0 Patchsoap1856-Latest

Resolved an issue in SOAP Execute when handling null field.

4.6.0snapsmrc362-Stable
  • Enhanced SOAP Execute Snap to handle a SOAP call with an empty response. 
  • Resolved an issue in SOAP Execute Snap that failed with an error in returning a response but returns an empty response. 
  • Resolved an issue in SOAP Execute Snap that caused the Snap to unsuccessfully parse XML schema from a valid WSDL when generating a SOAP envelope.
4.5.1soap1623-Latest
  • SOAP Execute Snap is updated to terminate a SOAP request after a number of attempts, and to successfully execute the Snap only if a success condition is met. The fields added are Maximum request attempts, Retry interval, & Success condition. For more information, see SOAP Execute.
  • Enhanced error handling in SOAP Execute Snap when generating customize envelope.
4.5.0snapsmrc344--

Resolved an issue in SOAP Execute Snap that occurred when connecting to ServiceNow.

Known Issue

  • Soap Execute Snap: This Snap currently does not support the wsdl:import statement. For wcf, the way to generate a single wsdl for a wcf wsdl url which ends in ?wsdl, is to change it to ?singleWsdl.
4.3.2---
  • Soap Execute Snap now returns HTTP header in output
  • Support WS-Security Draft 13 for a SOAP WSSE Account
  • Resolved an issue with SOAP WSSE Account. Authentication was rejected because <wsu:Created> DateTime value is not being correctly converted to UTC timezone.
4.3.1
--
  • Resolved a null pointer exception.
  • Added thread safety to XML library to prevent Null pointer exception.
-September 5, 2015 (4.2.2)--
  • Support added to return SOAP headers in SOAP Execute Snap.
  • Resolved an issue with SOAP Execute being unable to interpret MTOM response SOAP responses.
  • Migration impact: Output SOAP Envelope now defaults to false.
  • New setting: SSL Protocol
-August 7, 2015--
  • SOAP Execute Snap now disables importing XSDs if any are in a WSDL.
  • Resolved a Null pointer exception in SOAP Execute.
  • Resolved an issue with not being able to generate a template from Taleo WSDL.
  • Resolved a loader contraint violation issue in SOAP Execute when resolving method "org.apache.http.impl.client.HttpAuthenticator".
  • Resolved an issue with WSSE Account not working with SOAP Execute Snap
-June 27, 2015--
  • Timeout option required for SOAP Execute Snap.
  • Support for SOAP attachments.
-June 6, 2015--

SOAP Execute: resolved an issue with the SOAP WSSE account not working

-May 15, 2015--
  • SOAP Request failed for Hiperos WSDl
  • SOAP Execute: failure, resolution is not provided; Not loading issue
  • SOAP Snap failed for control character created by CSV Parser
  • SOAP Snap: updated error message when an invalid WSDL was selected
  • SOAP Snap output schema updated. Error and reason were added back to the output in addition to Fault code, detail entry, soap fault exception, and fault string
-

May 2, 2015

--

SOAP Snap: enhanced template generation

-January 2015--
  • WSSE Account type added.
  • Optional Trust all certificates property added.
-October 18, 2014--

Soap Execute does not work with Basic Auth header during configure phase

-September 5, 2014--

SOAP Execute: Encode Attribute was added as an optional setting for this Snap. When selected, the attributes from XSD will be differentiated with an '@' prefix in the input schema of this Snap.

-June 30, 2014--
  • Addressed the following issues:
    • SOAP Request: Default value should be given in the SOAP binding type property instead of blank.
    • SOAP Request: Document should be updated with SOAP Binding type Property.
    • SOAP Execute not generating the full template - including some required fields for D&B V2 services
    • SOAP Execute Snap: Write the envelope to the error view for debug purpose
    • SOAP Execute Snap fails to generate template
-May 2014--

SOAP Request updated to support input parameters in HTTP headers

-November 2013--

SOAP Request Snap

-August 2013--

SOAP Call Snap

Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.