Configuring Binary accounts
You must create Binary accounts to connect to data sources that you want to use in your Pipelines. You can configure your account from SnapLogic Platform using the Designer or Manager
Snap-Account Compatibility
Snaps in the Binary Snap Pack work with different accounts and protocols per the following table:
| Snap | AWS S3 Account | Azure Data Lake Storage Gen 2 OAuth2 Account - Binary | Azure Storage Account | Basic Auth Account | File Password Account | Google Sevice Account | Google Storage Account | Private Key Account | Public Key Account | S3 Dynamic Account | SMB Account | SSH Auth Account | Two-Factor Auth Account | Symmetric Crypto Account | Protocols Supported |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AES Decrypt | N/A | ||||||||||||||
| AES Encrypt | N/A | ||||||||||||||
| Blowfish Decrypt | N/A | ||||||||||||||
| Blowfish Encrypt | N/A | ||||||||||||||
| Compress | N/A | ||||||||||||||
| Decompress | N/A | ||||||||||||||
| Directory Browser |
|
||||||||||||||
| File Delete |
|
||||||||||||||
| File Operation |
|
||||||||||||||
| File Poller |
|
||||||||||||||
| File Reader |
|
||||||||||||||
| File Writer |
|
||||||||||||||
| Multi File Reader |
|
||||||||||||||
| Multipart Writer | Account not required | ||||||||||||||
| PGP Decrypt | N/A | ||||||||||||||
| PGP Encrypt | N/A | ||||||||||||||
| S3 File Reader |
|
||||||||||||||
| S3 File Writer |
|
||||||||||||||
| SAS Generator |
|
||||||||||||||
| Twofish Decrypt | N/A | ||||||||||||||
| Twofish Encrypt | N/A | ||||||||||||||
| Zipfile Read |
|
||||||||||||||
| Zipfile Write |
|
||||||||||||||
The following binary accounts support the listed protocol:
| Protocol | Account types |
|---|---|
| FTP and FTPS | Basic Auth |
| smb | SMB |
| wasb | Azure Storage |
| wasbs | Azure Storage |
| gs | Google Storage |
| adl | Azure Data Lake |
Warning: The FTPS file protocol works only in explicit mode. The implicit mode is not supported.