Versions Compared

Version Old Version 18 New Version 19
Changes made by

Ritu Sachdeva

Lakshmi Manda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this Page

Table of Contents
maxLevel2
absoluteUrltrue
excludeOlder Versions|Additional Resources|Related Links|Related Information

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 binary files:

  1. Click Create, then select JWT, then JWT Account.
  2. Supply an account label.

  3. Supply the necessary information.

  4. (Optional) Supply additional information on this account in the Notes field of the Info tab.
  5. Click Apply.

Account Types

Default value: [None]
Panel

JWT Account

Account Settings

value [None] value: [None]

Label

Required. User provided label for the account instance

JWT Issuer

Required. The principal that issued this JWT.

Default value: pipe.projectPath + '/' + pipe.label

Token TTL

The duration (in seconds) for which the token will be valid.

Minimum value: 60

Default value: 3600

Secret type


Default Value: KeyStore
Example: Secret key

Choose the Secret type. The available options are:

  • KeyStore

  • Secret key

Key Store


Default Value: None
Example: keystore.jks

Required. The location of the Key Store file, can be in SLDB, on the host machine that is hosting the JCC, or any other unauthenticated endpoint such as https.

 

KeyStore password


Default Value: None
Example: keystorepswd01

Required. Password for keystore. If the key associated with the alias has a password, that password should be the same as this KeyStore password.


Key Alias


Default

Value:

Key Alias

 None
Example: mykeyalias

Required. The alias of the secret key to use when signing token. 


Secret key


Default

Value: None
Example: secRETkey007!

Appears when you select Secret key for Secret type.

Specify the secret key to use to generate digital signatures.


Note

This field allows pipeline parameters. When you select a secret key, a JWT token is generated, which must be verified using a JWT Validate Snap.


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.

  • High: KeyStore password
  • Medium + High: KeyStore password
  • Low + Medium + High:  KeyStore password


Regarding KeyStore

There are multiple ways to specify the Key Store. It can be:

  1. Located on SLFS (by uploading the Key Store file)
  2. On the host machine that is hosting the JCC
  3. On an accessible web location

To generate a Key Store file, one can use the keytool utility that comes packaged with JDKs. Here're some useful keytool commands:

  • To create a key store with an AES key

    Code Block
    keytool -genseckey -keystore <keystore file name> -storetype jceks -storepass <store password> -keyalg AES -keysize 256 -alias <key alias>


  • To create a key store with 512 bit key

    Code Block
    keytool -genseckey -keystore <keystore file name> -storetype jceks -storepass <store password> -keyalg HMACSHA1 -keysize 512 -alias <key alias>


  • To import keys from one key store to another

    Code Block
    keytool -importkeystore -srckeystore <src keystore file> -srcstoretype jceks  -destkeystore <dest keystore file> -deststoretype jceks -deststorepass <dest store password>


  • To update the password for a key in a keystore

    Code Block
    keytool -storetype jceks -keypasswd -keystore <keystore file> -alias <key alias> -keypass <old key password> -new <new key password>


  • To list keys in a key store file

    Code Block
    keytool -list -v  -storetype jceks -keystore <keystore file>



Insert excerpt
JWT Snap Pack
JWT Snap Pack
nopaneltrue