CkJwe C++ Reference Documentation

CkJwe

Current Version: 10.0.0

An API for JSON Web Encryption (JWE). Provides the ability to create (encrypt) and decrypt JWE's.

Supported Algorithms:

  • RSAES OAEP 256 (using SHA-256 and MGF1 with SHA-256) encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • RSAES OAEP (using SHA-1 and MGF1 with SHA-1) encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • RSAES-PKCS1-V1_5 encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • Direct symmetric key encryption with pre-shared key A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM and A256GCM
  • A128KW, A192KW, A256KW encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • A128GCMKW, A192GCMKW, A256GCMKW encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • PBES2-HS256+A128KW, PBES2-HS384+A192KW, PBES2-HS512+A256KW with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM

Object Creation

// Local variable on the stack
CkJwe obj;

// Dynamically allocate/delete
CkJwe *pObj = new CkJwe();
// ...
delete pObj;

Properties

DebugLogFilePath
void get_DebugLogFilePath(CkString &str);
const char *debugLogFilePath(void);
void put_DebugLogFilePath(const char *ansiOrUtf8Str);

If set to a file path, causes each Chilkat method or property call to automatically append it's LastErrorText to the specified log file. The information is appended such that if a hang or crash occurs, it is possible to see the context in which the problem occurred, as well as a history of all Chilkat calls up to the point of the problem. The VerboseLogging property can be set to provide more detailed information.

This property is typically used for debugging the rare cases where a Chilkat method call hangs or generates an exception that halts program execution (i.e. crashes). A hang or crash should generally never happen. The typical causes of a hang are:

  1. a timeout related property was set to 0 to explicitly indicate that an infinite timeout is desired,
  2. the hang is actually a hang within an event callback (i.e. it is a hang within the application code), or
  3. there is an internal problem (bug) in the Chilkat code that causes the hang.

More Information and Examples
top
LastErrorHtml
void get_LastErrorHtml(CkString &str);
const char *lastErrorHtml(void);

Provides information in HTML format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.

top
LastErrorText
void get_LastErrorText(CkString &str);
const char *lastErrorText(void);

Provides information in plain-text format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.

top
LastErrorXml
void get_LastErrorXml(CkString &str);
const char *lastErrorXml(void);

Provides information in XML format about the last method/property called. If a method call returns a value indicating failure, or behaves unexpectedly, examine this property to get more information.

top
LastMethodSuccess
bool get_LastMethodSuccess(void);
void put_LastMethodSuccess(bool newVal);

Indicate whether the last method call succeeded or failed. A value of true indicates success, a value of false indicates failure. This property is automatically set for method calls. It is not modified by property accesses. The property is automatically set to indicate success for the following types of method calls:

  • Any method that returns a string.
  • Any method returning a Chilkat object, binary bytes, or a date/time.
  • Any method returning a standard boolean status value where success = true and failure = false.
  • Any method returning an integer where failure is defined by a return value less than zero.

Note: Methods that do not fit the above requirements will always set this property equal to true. For example, a method that returns no value (such as a "void" in C++) will technically always succeed.

top
NumRecipients
int get_NumRecipients(void);
Introduced in version 9.5.0.66

The number of recipients for this JWE.

top
PreferCompact
bool get_PreferCompact(void);
void put_PreferCompact(bool newVal);
Introduced in version 9.5.0.66

Controls whether the JWE Compact Serialization or JWE JSON Serialization is preferred when creating JWEs. The default value is true, which is to use compact serialization when possible. If multiple recipients exist, or if any unprotected headers exist, then JWE JSON Serialization is used regardless of this property setting.

top
PreferFlattened
bool get_PreferFlattened(void);
void put_PreferFlattened(bool newVal);
Introduced in version 9.5.0.66

Controls whether the flattened serialization is preferred when JWE JSON Serialization is used. The default value is true, which is to use the flattened serialization when possible. If multiple recipients exist, then the general (non-flattened) JWE JSON Serialization is used regardless of this property setting.

More Information and Examples
top
Utf8
bool get_Utf8(void);
void put_Utf8(bool newVal);

When set to true, all "const char *" arguments are interpreted as utf-8 strings. If set to false (the default), then "const char *" arguments are interpreted as ANSI strings. Also, when set to true, and Chilkat method returning a "const char *" is returning the utf-8 representation. If set to false, all "const char *" return values are ANSI strings.

top
VerboseLogging
bool get_VerboseLogging(void);
void put_VerboseLogging(bool newVal);

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
void get_Version(CkString &str);
const char *version(void);

Version of the component/library, such as "9.5.0.94"

More Information and Examples
top

Methods

Decrypt
bool Decrypt(int index, const char *charset, CkString &outStr);
const char *decrypt(int index, const char *charset);
Introduced in version 9.5.0.66

Decrypts a JWE and returns the original (decrypted) string content. The byte representation of the decrypted bytes is indicated by charset (such as "utf-8"). (The charset tells Chilkat how to intepret the decrypted bytes as characters.)

The index specifies which recipient key is used for decryption. (Most JWEs have only a single recipent, and thus the index is typically 0.)

Supported Algorithms:

  • RSAES OAEP 256 (using SHA-256 and MGF1 with SHA-256) encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • RSAES OAEP (using SHA-1 and MGF1 with SHA-1) encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • RSAES-PKCS1-V1_5 encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • Direct symmetric key encryption with pre-shared key A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM and A256GCM
  • A128KW, A192KW, A256KW encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • A128GCMKW, A192GCMKW, A256GCMKW encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • PBES2-HS256+A128KW, PBES2-HS384+A192KW, PBES2-HS512+A256KW with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM

Returns true for success, false for failure.

top
DecryptBd
bool DecryptBd(int index, CkBinData &bd);
Introduced in version 9.5.0.66

Decrypts the loaded JWE and appends the decrypted bytes to the contents of bd. The index specifies which recipient key is used for decryption. (Most JWEs have only a single recipent, and thus the index is typically 0.)

Returns true for success, false for failure.

More Information and Examples
top
DecryptSb
bool DecryptSb(int index, const char *charset, CkStringBuilder &contentSb);
Introduced in version 9.5.0.66

Decrypts the loaded JWE and appends the decrypted content to contentSb. The byte representation of the decrypted bytes is indicated by charset (such as "utf-8"). (This tells Chilkat how to interpret the bytes as characters.)

The index specifies which recipient key is used for decryption. (Most JWEs have only a single recipent, and thus the index is typically 0.)

Returns true for success, false for failure.

More Information and Examples
top
Encrypt
bool Encrypt(const char *content, const char *charset, CkString &outStr);
const char *encrypt(const char *content, const char *charset);
Introduced in version 9.5.0.66

Encrypts string content to produce a JWE. The byte representation of the content is indicated by charset (such as "utf-8").

Supported Algorithms:

  • RSAES OAEP 256 (using SHA-256 and MGF1 with SHA-256) encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • RSAES OAEP (using SHA-1 and MGF1 with SHA-1) encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • RSAES-PKCS1-V1_5 encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • Direct symmetric key encryption with pre-shared key A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM and A256GCM
  • A128KW, A192KW, A256KW encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • A128GCMKW, A192GCMKW, A256GCMKW encryption with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM
  • PBES2-HS256+A128KW, PBES2-HS384+A192KW, PBES2-HS512+A256KW with A128CBC-HS256, A192CBC-HS384, A256CBC-HS512, A128GCM, A192GCM, A256GCM

Returns true for success, false for failure.

top
EncryptBd
bool EncryptBd(CkBinData &contentBd, CkStringBuilder &jweSb);
Introduced in version 9.5.0.66

Encrypts the contents of contentBd to produce a JWE that is appended to the contents of jweSb. (This method provides the means to produce a JWE from binary content.)

Returns true for success, false for failure.

More Information and Examples
top
EncryptSb
bool EncryptSb(CkStringBuilder &contentSb, const char *charset, CkStringBuilder &jweSb);
Introduced in version 9.5.0.66

Encrypts the contents of contentSb to produce a JWE that is appended to the contents of jweSb. The byte representation of the string to be encrypted is indicated by charset (such as "utf-8").

Returns true for success, false for failure.

More Information and Examples
top
FindRecipient
int FindRecipient(const char *paramName, const char *paramValue, bool caseSensitive);
Introduced in version 9.5.0.66

Finds the index of the recipient with a header parameter (paramName) equal to a specified value (paramValue). Returns -1 if no recipient contains a header with the given name/value. If caseSensitive is true, then the header param name/value comparisons are case sensitive. Otherwise it is case insensitive.

The procedure for decrypting a JWE with multiple recipients is the following:

  1. Load the JWE via one of the Load* methods.
  2. Find the recipient index by some identifying header paramter. The typical case is via the "kid" header parameter. ("kid" is an arbitrary key ID applications can assign to identify keys.)
  3. Set the key for decryption at the found index by calling SetPrivateKey, SetWrappingKey, or SetPassword, depending on the type of key wrapping that is employed.
  4. Call Decrypt, DecryptSb, or DecryptBd to decrypt for the recipient (and key) at the given index.

More Information and Examples
top
GetHeader
bool GetHeader(CkJsonObject &json);
Introduced in version 9.5.0.89

Returns the JSON header from the JWE. The JSON header is loaded into json.

Returns true for success, false for failure.

top
GetProtectedHeader
bool GetProtectedHeader(CkJsonObject &json);
Introduced in version 9.5.0.89

Returns the shared protected JSON header from the JWE. The shared protected header is loaded into json.

Returns true for success, false for failure.

top
LoadJwe
bool LoadJwe(const char *jwe);
Introduced in version 9.5.0.66

Loads the contents of a JWE.

Returns true for success, false for failure.

More Information and Examples
top
LoadJweSb
bool LoadJweSb(CkStringBuilder &sb);
Introduced in version 9.5.0.66

Loads the contents of a JWE from a StringBuilder object.

Returns true for success, false for failure.

More Information and Examples
top
SetAad
bool SetAad(const char *aad, const char *charset);
Introduced in version 9.5.0.66

Sets the optional Additional Authenticated Data. This is only used for non-compact serializations. The charset specifies the character encoding (such as "utf-8") to be used for the byte representation for the additional authenticated data.

Returns true for success, false for failure.

top
SetAadBd
bool SetAadBd(CkBinData &aad);
Introduced in version 9.5.0.66

Sets the optional Additional Authenticated Data. This is only used for non-compact serializations. This method provides a way for binary (non-text) additional authenticated data to be used.

Returns true for success, false for failure.

top
SetPassword
bool SetPassword(int index, const char *password);
Introduced in version 9.5.0.66

Sets the PBES2 password for key encryption or decryption. This is for the case where the content encryption key (CEK) is encrypted using PBES2. An PBES2 password should be used in the cases where the "alg" header parameter value is equal to one of the following:

PBES2-HS256+A128KW
PBES2-HS384+A192KW
PBES2-HS512+A256KW
The index is the index of the recipient, where the 1st recipient is at index 0. (The typical use case for JWEs is for a single recipient.)

Returns true for success, false for failure.

top
SetPrivateKey
bool SetPrivateKey(int index, CkPrivateKey &privKey);
Introduced in version 9.5.0.66

Sets a private key for RSA key unwrapping/decryption. This is for the case where the content encryption key (CEK) is encrypted using RSA. An RSA private key should be used for decrypting in the cases where the "alg" header parameter value is equal to one of the following:

RSA1_5
RSA-OAEP
RSA-OAEP-256
RSA-OAEP-384  (added in Chilkat v9.5.0.71)
RSA-OAEP-512  (added in Chilkat v9.5.0.71)
The index is the index of the recipient, where the 1st recipient is at index 0. (The typical use case for JWEs is for a single recipient.)

Returns true for success, false for failure.

More Information and Examples
top
SetProtectedHeader
bool SetProtectedHeader(CkJsonObject &json);
Introduced in version 9.5.0.66

Sets the JWE Protected Header.

Returns true for success, false for failure.

top
SetPublicKey
bool SetPublicKey(int index, CkPublicKey &pubKey);
Introduced in version 9.5.0.66

Sets a public key for RSA key wrapping encryption. This is for the case where the content encryption key (CEK) is encrypted using RSA. An RSA public key should be used when encrypting for the cases where the "alg" header parameter value is equal to one of the following:

RSA1_5
RSA-OAEP
RSA-OAEP-256
The index is the index of the recipient, where the 1st recipient is at index 0. (The typical use case for JWEs is for a single recipient.)

Returns true for success, false for failure.

More Information and Examples
top
SetRecipientHeader
bool SetRecipientHeader(int index, CkJsonObject &json);
Introduced in version 9.5.0.66

Sets a per-recipient unprotected header. This method would only be called if the JWE is for multiple recipients. The 1st recipient is at index 0.

Returns true for success, false for failure.

top
SetUnprotectedHeader
bool SetUnprotectedHeader(CkJsonObject &json);
Introduced in version 9.5.0.66

Sets the JWE Shared Unprotected Header.

Returns true for success, false for failure.

top
SetWrappingKey
bool SetWrappingKey(int index, const char *encodedKey, const char *encoding);
Introduced in version 9.5.0.66

Sets the AES wrapping key for encryption or decryption. This is for the case where the content encryption key (CEK) is encrypted using AES Key Wrap or AES GCM. An AES key should be used in the cases where the "alg" header parameter value is equal to one of the following:

A128KW
A192KW
A256KW
A128GCMKW
A192GCMKW
A256GCMKW
dir
The index is the index of the recipient, where the 1st recipient is at index 0. (The typical use case for JWEs is for a single recipient.)

Note: This method also sets the shared direct symmetric key for the case when the "alg" is equal to "dir". In this case, the key specified is not actualy a key encryption key, but is the direct content encryption key.

The encoding indicates the representation, such as "base64", "hex", "base64url", etc. of the encodedKey.

Returns true for success, false for failure.

top