This page is no longer maintained (Dec 15, 2025). For the most current information, go to Configuring SOAP Accounts.

1 Account Configuration
2 Account Types
- 2.1 SOAP Basic Auth
  - 2.1.1 Account Encryption
- 2.2 SOAP NTLM Account
  - 2.2.1 Account Encryption
- 2.3 SOAP SSL Account
  - 2.3.1 Account Encryption
- 2.4 SOAP WSSE Account
  - 2.4.1 Account Encryption

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:

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

Account Types

SOAP Basic Auth

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

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

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://...

The supported formats for KeyStore are: JKS, JCEKS and PKCS12.

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

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.