Configuring Binary Accounts


Snap-Account Compatibility

Snaps in the Binary Snap Pack work with different accounts and protocols per the following table.

SnapAWS S3 AccountAzure Data Lake AccountAzure Storage AccountBasic Auth AccountFile Password AccountGoogle Service AccountGoogle Storage AccountPrivate Key AccountPublic Key AccountS3 Dynamic AccountSMB AccountSSH Auth AccountTwo-Factor Auth AccountSymmetric Crypto AccountProtocols Supported
AES Decrypt

ADL
AES EncryptN/A
Blowfish DecryptN/A
Blowfish EncryptN/A
CompressN/A
DecompressN/A
Directory Browser
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
File Delete
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
File Operation
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
File Poller
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
File Reader
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
File Writer
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
Multi File Reader
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
Multipart ReaderN/A
Multipart WriterN/A
PGP DecryptN/A
PGP EncryptN/A
S3 File Reader
  • S3
S3 File Writer
  • S3
SAS Generator
  • WASB
  • WASBS
Twofish DecryptN/A
Twofish EncryptN/A
ZipFile Read
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB
ZipFile Write
  • S3
  • ADL
  • WASB
  • WASBS
  • FTP
  • SFTP
  • FTPS
  • HTTP
  • HTTPS
  • GS
  • SMB


Account types supported by each protocol are as follows:

ProtocolAccount types
sldbno account
s3AWS S3, S3 Dynamic
ftpBasic Auth
sftpBasic Auth, SSH Auth 
ftpsBasic Auth
hdfsno account
httpno account
httpsoptional account
smbSMB
fileno account
wasbAzure Storage
wasbs

Azure Storage

gs

Google Storage

adl

Azure Data lake 

The FTPS file protocol works only in explicit mode. The implicit mode is not supported.

Configuring Binary Accounts

You can configure your binary accounts in SnapLogic using either the Designer or Manager.

Using SnapLogic Designer

Drag a binary Snap to the Canvas and click the Snap to open its settings. Click the Account tab. You can now either use an existing account or create a new one.

Selecting an existing account

SnapLogic organizes and displays all accounts to which you have access, sorting them by account type and location. To select an existing account:

  1. Click the  icon to view the accounts to which you have access and select the account that you want to use. 

  2. Click .

Creating an account

  1. Click Add Account in the Account Reference dialog.

  2. Select the Location in which you want to create the account, select the account type, and click ContinueThe Add Account dialog associated with the account type appears.


  3. Enter the required account details. For detailed guidance on how to provide information associated with each account type, use the following links:

    Enter additional information on this account in the Notes field of the Info tab. This will help you–and other users–understand the purpose of the account, especially if there are multiple accounts of the same type.

  4. Click Validate to verify the account, if the account type supports validation.

  5. Click Apply to complete configuring the binary account.

Using SnapLogic Manager

Use Manager to create accounts without associating them immediately with Pipelines.

Accounts in SnapLogic are associated with projects. You can use accounts created in other projects only if you have at least Read access to them.

  1. In the left pane, browse to the project in which you want to create the account and click CreateAccount Binary, followed by the appropriate account type.

    The Create Account dialog associated with the selected account type appears. 

  2. Repeat the steps numbered 3 through 5 in the previous section.


Avoid updating account credentials while Pipelines using that account are executing. This may lead to unexpected results, including locking your account.

Snap Pack History


 Click to view/expand


Release Snap Pack VersionDateTypeUpdates
August 2024438patches28197 Latest
  • Fixed an issue in the Binary Snap Pack that caused intermittent errors on the Groundplex nodes when using the SMB protocol. The errors occurred when multiple IPs were returned for the same address, and one of the IPs was unreachable by the SMB server
  • Fixed an issue in the Directory Browser Snap where a mount error was displayed if the hostname contained an underscore, resulting in an empty hostname in the SMB URL.

August 2024

main27765

 

Stable

Upgraded the org.json.json library from v20090211 to v20240303, which is fully backward compatible.

May 2024437patches27146 LatestEnhanced the Azure Storage Account with Managed Identity, which provides applications with an automatically managed identity for connecting to resources that support Microsoft Entra ID authentication.
May 2024437patches26873 LatestFixed an issue with the File Poller Snap where the Snap applied a case-sensitive filter in the Windows operating system.
May 2024437patches26592 Latest

Enhanced the Decompress Snap to support encrypted and unencrypted ZIP and 7z files through the new File Password Account type.

May 2024main26341 Stable

The Azure Data Lake Account has been removed from the Binary Snap Pack because Microsoft retired the Azure Data Lake Storage Gen1 protocol on February 29, 2024. We recommend replacing your existing Azure Data Lake Account with other Azure Accounts.

February 2024436patches25711 Latest

Fixed an SMB (server message block) connectivity issue within the Binary Snap Pack, as the incorrect name provided by the SMB client did not match the Windows cluster virtual name, affecting the SPN (service principal name) connection.

February 2024436patches25332 Latest

Fixed a null pointer exception in the Public Key Account for Binary Snap Pack when the Public Key field value is null. Now, the account displays a