Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel1
outlinefalse
typeflat
printablefalse

...

...

Dot Releases: Snaps

Snap Pack

Date

Snap Pack Version

Updates

Salesforce

439patches29014

Fixed an issue with the Salesforce Lookup Snap that did not route errors to the error pipeline when the Route Error Data to Error View was enabled.

Oracle

439patches29008

Fixed an issue with Oracle Execute, Select, and Stored Procedure Snaps where the data was displayed in an unexpected structure and without the actual row address value when querying table columns of ROWID type. Now, the Snaps handle the ROWID type columns correctly to prevent the display of the nested output when ROWID is combined in the query with other selected columns.

Note

Breaking change:

With the 439patches29008Snap Pack version if any of your existing Oracle pipelines use the encoded ROWID(by manually handling the Base64 encoded data), your pipelines might break. To prevent your pipelines from failing, you must update your Snap Pack version to the latest version.

Behavior change:

Earlier, the ROWID columns were displayed in binary (Base64 encoded data) form in the output. With the 439patches29008, the Oracle Execute and Select Snaps display the ROWID columns in string form in the output (which can be used for other operations downstream).

Upgrading to this Release

...

  • System Configuration now includes the Git Integration page for selecting a Git provider. This supports continuous integration and continuous development (CI/CD) across different environments. Learn more.

    image-20241101-072520.png
  • In the Security section, configure Enhanced Account Encryption (EAE) from the Account encryption page. With a subscription to EAE and use of a Groundplex, sensitive account data is encrypted with a public key in the SnapLogic domain control plane and decryped decrypted with a private key on the Groundplex. Learn more.

    account-encryption.png

  • In the Application settings section, configure Asset catalog visibility. The Asset catalog is available to enterprise SnapLogic customers by request. Learn more.

    image-20241106-104259.png

...

...

New Content

  • Enhanced the OAuth 2.0 Client Credentials article with an Okta integration example.

Monitor

Enhancements

  • The Integration catalog, available to enterprise SnapLogic customers by request, is now the Asset catalog. It includes the following enhancements:

    • With the new API described in the Platform section, you can add custom metadata columns to the table of tasks and add, update, or delete existing custom metadata values from a task.

    • With the new configuration described in the Admin Manager section, you can allow all users view-only access to the Asset catalog or restrict it to admins.

    • The new Pipelines tab displays standard pipeline metadata:

      catalog-pipelines-tab.png
    • Task details are easier to read, with important information moved to the header and execution statistics split out into a new tab:

      catalog-task-general-tab.png
    • The Custom tab on the Task details pane includes the ability to edit custom metadata values:

      catalog-task-edit-metadata2.png

...

Important Updates from Snowflake

Deprecated Drivers:

As of February 1, 2024, Snowflake has ceased support of older driver versions in compliance with its Support Policy. You must upgrade to the latest driver version to access important security, performance, and functionality improvements. Ensure that your Snowflake pipelines use the Snowflake JDBC Driver v3.13.27 or a higher version. Learn how to check your current driver version. The Snowflake Snap Pack is bundled with the 3.16.0 JDBC driver, but if you are using your own version, it may be deprecated in accordance with Snowflake Guidelines.

Security Policies:

Snowflake recently signed the Cybersecurity and Infrastructure Security Agency (CISA) Secure By Design Pledge. In line with CISA’s Secure By Design principles, Snowflake recently announced several security enhancements in their platform — most notably the general availability of Trust Center and a new Multi-Factor Authentication (MFA) policy.

Effective October 2024, MFA will be enforced by default for all human users in any new Snowflake account. Service users (accounts designed for service-to-service communication) will not be subject to this MFA requirement.

Basic Authentication Accounts:

If you currently use Basic authentication to access Snowflake, we recommend one of the following:

  • Update your password to a maximum of 14 characters and a minimum of 8, and ensure it does not match any of the previous five passwords. Learn more.

  • Migrate to Key-Pair authentication: This method involves generating a public and private key pair, where the private key is securely stored and the public key is registered with your Snowflake account.

  • Migrate to OAuth2 authentication: This is a widely adopted standard for secure delegated access. It allows applications to obtain limited access to user accounts on an HTTP service, facilitating safer and more manageable authentication flows.

Implementing the above recommendations will secure your data and protect sensitive data, ensuring compliance with Snowflake's updated security policies. Learn more. For questions, contact support@snaplogic.com.

Breaking Changes

Note

JDBC Snap Pack:

Reltio Account deprecation by the end of October 2024

  • Reltio has announced the deprecation of basic authentication using username and password for API access by the end of October 2024 to enhance their platform security. All customers must adopt client credentials and stop using username/password for API access immediately. Reltio will disallow API access using username/password by the end of October 2024. Client credentials are required for any integration or API usage with Reltio.

  • Consequently, SnapLogic deprecated the Reltio Account in the October 2024 release. Any existing Reltio pipelines that rely on the current Reltio Account that uses a username/password for API access will not be supported by Reltio. To ensure the continuity of your pipelines, we recommend that you use the Reltio OAuth2 Account.

...