You can either use keydata/format/options from the plugin configuration or on each action. Configuration on action supercedes plugin configuration.

Set the operation value on the operation field, as text (can be dynamic). Available operations: 'encrypt', 'encrypt private', 'decrypt, 'decrypt public', 'sign', 'verify'.




Plugin parameters info:


𝐊𝐄𝐘𝐃𝐀𝐓𝐀                                                                    --------------------------------------------------------------------------------- 

{string|object} — parameters for generating key or the key in one of supported formats.

- key in PEM string
- Object contains key components

You can leave this empty at the global and function level and generate an empty key.

You can also autogenerate a key, using an object with format: {b: <keyLength>} ie {b: 512}. See advanced options for more parameters used in key generation.

You can input the key as a string in PEM format:

'-----BEGIN RSA PRIVATE KEY-----MIIBOQIBAAJAV.......'




𝐎𝐏𝐓𝐈𝐎𝐍𝐒                                                                      --------------------------------------------------------------------------------- 


Json object with following fields:


• environment (please observe: use lowercase values) — working environment    (default
  autodetect):                                                        

      ○ 'browser' — will run pure js      implementation of
                                  RSA algorithms.                            

      ○ 'node' for nodejs >= 0.10.x or      io.js >= 1.x —
                                provide some native      methods like
                                sign/verify and      encrypt/decrypt.                                                                                                       
• encryptionScheme — padding scheme for    
 encrypt/decrypt. Can be 'pkcs1_oaep'    or 'pkcs1'. Default
 'pkcs1_oaep'.                                                       


                                                                        • signingScheme — Object containing two parts, scheme used for    signing and
  verifying. Can be 'pkcs1'    or 'pss'. And hash (see supported hash algos below). IE:   {"signingScheme":{"scheme":"pss","hash":"sha256"}}                                                                                                         
Notice: This lib supports hash  algorithms: 'md5', 'ripemd160', 'sha1', 'sha256', 'sha512' in browser and node  environment and additional 'md4', 'sha', 'sha224', 'sha384' in node only.



𝗙𝗢𝗥𝗠𝗔𝗧 𝗦𝗧𝗥𝗜𝗡𝗚 𝗦𝗬𝗡𝗧𝗔𝗫                                          --------------------------------------------------------------------------------- 

Format string composed of several parts:
scheme-[key_type]-[output_type]                                                                                                       

• Scheme — NodeRSA supports multiple format schemes for import/export keys:                                                                                                                     
          ○ 'pkcs1' — public key starts from '-----BEGIN RSA
              PUBLIC KEY-----' header and private key starts from
              '-----BEGIN RSA PRIVATE KEY-----' header                                                                                                    
         ○ 'pkcs8' — public key starts from '-----BEGIN PUBLIC
             KEY-----' header and private key starts from '-----
             BEGIN PRIVATE KEY-----' header                                                                                                                  
         ○ 'openssh' — public key starts from 'ssh-rsa' header
             and private key starts from '-----BEGIN OPENSSH
             PRIVATE KEY-----' header                                                                                                        

• Key type — can be 'private' or 'public'. Default 'private'                                                                            

• Output type — can be:                                                ○  'pem' — Base64 encoded string with header and
                            footer. Used by default.                              ○ 'der' — Binary encoded key data.                                                                                          

Notice: For import, if keyData is PEM string, you cannot specify format, but if you provide keyData as DER you must specify it in format string.                                                                                                   

𝗦𝗛𝗢𝗥𝗧𝗖𝗨𝗧𝗦 𝗔𝗡𝗗 𝗘𝗫𝗔𝗠𝗣𝗟𝗘𝗦                                                                                                        'private' or 'pkcs1' or 'pkcs1-private' == 'pkcs1-private-pem' — private key encoded in pcks1 scheme as pem string.                                                                            

'public' or 'pkcs8-public' == 'pkcs8-public-pem' — public key encoded in pcks8 scheme as pem string.                                                                                        

'pkcs8' or 'pkcs8-private' == 'pkcs8-private-pem' — private key encoded in pcks8 scheme as pem string.                  


'pkcs1-der' == 'pkcs1-private-der' — private key encoded in pcks1 scheme as binary buffer.                                                                                                    

'pkcs8-public-der' — public key encoded in pcks8 scheme as binary buffer.