Configuring Anaplan Accounts

On this Page

Overview

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

Anaplan CA Certificates Migration

Anaplan is extending the deadline to migrate to Certificate Authority (CA) certificates to February 26, 2020 when Anaplan will update their production certificate. This will replace validation for Anaplan certificates, wherein existing Anaplan certificates will cease to work once this certificate is issued. This new certificate is to be used for existing clients on the legacy certificate authentication. This certificate will NOT work on clients using the CA certificates. Anaplan recommends that customers update their integration clients to a version that supports Certificate Authentication 2.0 that uses a CA certificate.

What are we doing?

We have upgraded our Anaplan Snap Pack to v2.0 APIs as of SanpLogic Release 4.15 (November, 2018). The upgraded Anaplan Snap Pack only supports v2.0 APIs with basic and certificate authority authentication, and does NOT support the Anaplan-generated certificate option. 

In basic authentication, the username and password is sent to the Anaplan Server, over SSL. Certificate authority authentication requires a certificate and a private key to verify the user to the Anaplan Server. To support this, Certificate file and Certificate der properties are replaced with External certificate file, External certificate contents, and External private key properties that require a CA-supplied certificate to authenticate. The Anaplan certificate is stored locally and on the Anaplan server. The private key is never sent to the Anaplan server and is used to generate a one-time passcode (nonce) that is sent along with the certificate. The public key portion of the certificate is used to verify the contents of the nonce and validate the user.

We recommend you to plan ahead and either switch to basic authentication or have the certificate authority authentication ready by February 26, 2020. Contact support@snaplogic.com if you face any issues while migrating to basic or CA authentication.

How can you migrate to CA-signed certificates?

Prerequisites

Purchase and implement a certificate chain that meets the following requirements:

  • Starts from your user certificate to the root CA and ends at a supported Public Root CA.
  • Conforms to the X-509 public-key certificates.
  • Is generated using the RSA-2048–or stronger–algorithm.
  • Contains your email address in either of the following fields:
    • The X509v3 Subject Alternative Name field (preferred).
    • The EMAILADDRESS field in the Subject.
      Set the email address using the EMAILADDRESS attribute and not the CommonName attribute.

  • Contains a X509v3 Key Usage Digital Signature bit.
    Anaplan ignores all other bits.

  • Provides a way to confirm revocation using the Certificate Revocation List (CRL) or Online Certificate Status Protocol (OCSP).

Uploading the certificate

  1. Login to Anaplan Front Door with your credentials.

  2. Click  and select Administration.


  3. In the Administration menu, click Security > Certificates > Add Certificates.

    The Add Certificate dialog box appears.

  4. Browse and select your certificate files and click Import Certificates to upload them to the Anaplan server.

    You can now see the newly added certificate in the Certificates list.

Action required by you

Depending on the authentication method you use, perform the steps mentioned in the following table.

Authentication methodAction required with the updated Anaplan Snap Pack
Basic username and passwordNo action required.
CA certificateUpdate the Anaplan Account settings and enter relevant information in External certificate file, External certificate contents, and External private key properties. See Creating an Account, below, for more details.
Self-signed Anaplan CertificateOnce you upgrade your Snaplex instances to 4.20, you must roll back to the previous version of the Anaplan Snap Pack. Click here for instructions on roll back.
Anaplan certificate expires on February 26, 2020. You must download the new certificate and update the Anaplan Snap account with the new certificate. Click here for instructions to download the new Anaplan certificate.

Creating an Account

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 Anaplan account: 

  1. Click Create, then select Anaplan > Anaplan Account.
  2. Enter an account label.
  3. For basic authentication, enter the UsernamePassword, and Anaplan hostname
  4. (Optional) Supply additional information on this account in the Notes field of the Info tab.
  5. Click Apply


Anaplan Account

Label

Required. User provided label for the account instance.

Username


Required. The name for this account. This property is mandatory for basic authentication.

Default value: None

Password


Required. The password for the account. This property is mandatory for basic authentication.

Default value: None

Anaplan hostname


Required. The hostname for Anaplan REST API service.

Example: https://api.anaplan.com

Default valuehttps://api.anaplan.com

External certificate file

Link of the certificate file that you have uploaded.

You can use a certificate file instead of a username/password to simplify login. Click  to select the file and upload it into SnapLogic. Specifying External certificate contents is more secure than specifying the External certificate file because the certificate content is encrypted; whereas an uploaded certificate file is not encrypted.

Default value: None

External certificate contents

Specifies the contents of your certificate file. 

The certificate typically has the following format:

-----BEGIN CERTIFICATE-----
<certificatecontent_string>
-----END CERTIFICATE-----

Specifying External certificate contents is more secure than specifying the External certificate file because the certificate content is encrypted; whereas an uploaded certificate file is not encrypted.

Default value: None

External private key

Specifies the plain-text version of your private key.

If you have an encrypted private key, you must decrypt it using OpenSSL and the passphrase that was used for encryption. Perform the following steps in a terminal window to get the plain-text version of your private key:

  1. openssl rsa -in [file1.key] -out [file2.key]

    [file1.key] and [file2.key] are key files. [file1.key] contains the private key in binary format, and [file2.key] contains the plain-text output version that begins with -----BEGIN RSA PRIVATE KEY----- and ends with -----END RSA PRIVATE KEY-----.

  2. Enter the passphrase.   
  3. Copy the contents of [file2.key] and paste it in the External private key field.

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:

  • HighPassword
  • Medium + HighUsername, password
  • Low + Medium + HighUsername, password


Troubleshooting

If a validation error occurs after you enter the certificate and private key in Accounts, verify the following:

  • Check the certificate format. It must be in plain text and start with -----BEGIN CERTIFICATE----- and end with -----END CERTIFICATE-----.
  • Check the private key format. It must be in plain text and start with -----BEGIN RSA PRIVATE KEY----- and end with -----END RSA PRIVATE KEY-----.

Snap Pack History

 Click to view/expand
ReleaseSnap Pack Version DateTypeUpdates
4.29main15993 StableUpgraded with the latest SnapLogic Platform release.
4.28main14627 StableUpgraded with the latest SnapLogic Platform release.
4.27427patches13160 Latest

Fixed the issue with Anaplan Snaps, where the log messages were stored in jccoutput.log file instead of jcc.json file, and updated the dependent libraries.

4.27

main12833

 

Stable

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

Added the following fields to the Anaplan Write Snap:

  • Override server settings
  • Separator
  • Text Delimiter
4.25main9554 StableNo updates made.
4.24424patches9313 LatestFixed an issue related to Index out of range in the Anaplan Upload Snap when the separator is not present or does not match the one in the upload file.
4.24main8556 StableNo updates made.
4.23 

main7430

 

Stable

No updates made.

4.22422patches7392
 
Latest

Fixed the Snap Pack error handling issue by reverting the getChunk method, that returns a variant that contains all or a part of the contents of a large text or binary data Field object, of 1.4.4.2 jar version to 1.4.4.1 jar version and upgraded the jar version to 1.4.4.3.

4.22422patches6561
 
Latest
  • Fixed the Anaplan Snaps by displaying the same value for both Task ID and Task Name, by following the Anaplan client SDK.
  • Enhanced the Anaplan Snaps by allowing you to provide interchangeable inputs for the following fields: 
    • Workspace ID and Workspace Name
    • Model ID and Model Name

      Introduces a suggestible option that enables you to select the Workspace Name and Model Name.

4.22main6403
 
Stable

No updates made.

4.21421patches5851
 
Latest

Fixed the Anaplan Action Snap that outputs the same value for TaskID and TaskName parameters.

4.21snapsmrc542
 
StableNo updates made.
4.20snapsmrc535
 
StableNo updates made
4.19snaprsmrc528
 
Latest

Removed the suggestion button from the Workspace and Model fields in the Snap Settings dialog. Hence, you need to enter the field values manually.  

4.18snapsmrc523
 
Stable

No updates made.

4.17Anaplan7422
 
Latest

Fixed an issue with the Anaplan Read Snap wherein the Snap pulls archived and deleted models.

4.17ALL7402
 
Latest

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

4.17snapmrc515
Latest

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

4.16snapsmrc508
 
Stable

No updates made. Automatic rebuild with a platform release.

4.15snapsmrc500
 
Latest
  • To support Anaplan v2.0 API, we have enhanced the Anaplan Account configuration.
  • Added retry capability to Anaplan Action, Read, Write, and Upload Snaps that allow you to handle connection timeouts during Pipeline execution.
4.14anaplan6247

 

Latest

Added a new property, Override server settings, to override a few settings saved on Anaplan's server.

4.14anaplan5742
 
Latest

Fixed an issue where certain JCC-logging configurations had conflicts in class loading that resulted in inaccurate log information.

4.14snapsmrc490
 
Stable

No updates made. Automatic rebuild with a platform release.

4.13

snapsmrc486

 
Stable

No updates made. Automatic rebuild with a platform release.

4.12

snapsmrc480

 
StableNo updates made. Automatic rebuild with a platform release.
4.11snapsmrc465
 
StableNo updates made. Automatic rebuild with a platform release.
4.10

snapsmrc414

 
StableNo updates made. Automatic rebuild with a platform release.
4.9snapsmrc405
 
Latest
  • Added connection retry logic to Anaplan Action Snap.
  • "Re-submission of chunks" logic added to Anaplan Upload Snap.
4.8

snapsmrc398

 
Stable
  • No updates made. Automatic rebuild with a platform release.
  • Info tab added to accounts.
4.7

anaplan2179

 
Latest

Improved suggest lookup of Anaplan Snaps server files setting.

4.7

snapsmrc382

 
Latest

Updated the Anaplan Action Snap with a new output handling mechanism, Stream errors. Additionally, starting from 4.7 release, the default output handling mechanism is Stream errors. Prior to 4.7 release, the default mechanism was AllSuccess.

4.6

anaplan1874

 
Latest

Improved the error doc schema and error handling.

4.6

anaplan1870

  
Latest

Implemented new "Stream errors" mode.

4.6

anaplan1863

 
Latest

Resolved an issue with the Anaplan Action Snap failing with Java Heap Space.

4.6

snapsmrc362

 
Latest

Extended support for a der encoded representation of Anaplan Certificate for Anaplan account validation. Anaplan Action Snap is enhanced to support handling of output during an import action. If an import operation is unsuccessful, rows without an error are written to the output view, and rows with an error are written to the error view.

4.5.1


 
Stable

No updates made. Automatic rebuild with a platform release.

4.5

snapsmrc344

 
Latest
  • Resolved an issue with some Anaplan Snaps stopping on error even when an error view was enabled.
  • Improved error handling and output information to the Snaps in the Anaplan Snap Pack.
  • Support for Upload only operation in Anaplan Write Snap to upload a file to a server without running an import job.
  • Doc Enhancement: Examples added to Anaplan Snap documentation.

4.4.1


 
Latest

Anaplan Action Snap updated to include "resolution" in error output.

4.4


 
Latest

Resolved a "String index out of range" issue in the Anaplan Write Snap.

4.3.2


 
Latest
  • NEW! Anaplan Upload Snap
  • Anaplan Write now outputs more details to error view.
  • Resolved an issue in the Anaplan Read Snap where the suggested values for Export ID came back null.
  • Resolved an issue with the Anaplan Write Snap failing when writing to the error output view.
  • Resolved an issue with the Anaplan Action Snap not showing a list of the processes during Suggest.

4.3.1


 
Latest
  • Resolved an issue with Anaplan Write Snap's error handling in some cases producing inaccurate information.
  • Resolved null pointer exceptions in the Write Snap.
  • Server filename is now suggestible.
  • Migration impact: The output of the Write Snap is now a document instead of a string. Any pipelines using Anaplan Write along with a downstream Snap that is parsing the Anaplan Write output it will have to be reworked to use the new document map.
4.3
 
Latest

Migration Impact: The Anaplan Read Snap now writes the Anaplan file data read into the binary output view as a stream. This was done to resolve an issue with the Snap generating all column values into a single column.4.2.2


4.2.1


 
Latest
  • Resolved an issue with the Anaplan Write Snap skipping the first row.
  • Resolved an Anaplan Exception when writing from a database to Anaplan.
  • Resolved an issue with requests routing to error view but the file getting imported into Anaplan instance.
  • Migration Impact: The Anaplan Read Snap now writes the Anaplan file data read into the binary output view as a stream. This was done to resolve an issue with the Snap generating all column values into a single column.


June 2015 Latest

Anaplan action Snap should work for Anaplan processes as well.June 6, 2015 (2015.20)



March 2015

Latest

Anaplan accounts now work with Anaplan certificates



December 2014

Latest

NEW! Anaplan Action & Write



October 2014

Latest

NEW! Anaplan Read (Beta)