Jwt Unicode C Reference Documentation
Jwt
Current Version: 10.1.2
A class for signing and verifying JWT's (JSON Web Tokens).
Create/Dispose
HCkJwtW instance = CkJwtW_Create(); // ... CkJwtW_Dispose(instance);
Creates an instance of the HCkJwtW object and returns a handle ("void *" pointer). The handle is passed in the 1st argument for the functions listed on this page.
Objects created by calling CkJwtW_Create must be freed by calling this method. A memory leak occurs if a handle is not disposed by calling this function. Also, any handle returned by a Chilkat "C" function must also be freed by the application by calling the appropriate Dispose method, such as CkJwtW_Dispose.
Properties
AutoCompact
void CkJwtW_putAutoCompact(HCkJwtW cHandle, BOOL newVal);
If TRUE, the JSON passed to CreateJwt and CreateJwtPk will be compacted to remove unnecessary whitespace. This will result in the smallest possible JWT. The default value is TRUE.
topDebugLogFilePath
void CkJwtW_putDebugLogFilePath(HCkJwtW cHandle, const wchar_t *newVal);
const wchar_t *CkJwtW_debugLogFilePath(HCkJwtW cHandle);
If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.
Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.
Possible causes of hangs include:
- A timeout property set to 0, indicating an infinite timeout.
- A hang occurring within an event callback in the application code.
- An internal bug in the Chilkat code causing the hang.
LastErrorHtml
const wchar_t *CkJwtW_lastErrorHtml(HCkJwtW cHandle);
Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastErrorText
const wchar_t *CkJwtW_lastErrorText(HCkJwtW cHandle);
Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
LastErrorXml
const wchar_t *CkJwtW_lastErrorXml(HCkJwtW cHandle);
Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastMethodSuccess
void CkJwtW_putLastMethodSuccess(HCkJwtW cHandle, BOOL newVal);
Indicates the success or failure of the most recent method call: TRUE means success, FALSE means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages.
topUncommonOptions
void CkJwtW_putUncommonOptions(HCkJwtW cHandle, const wchar_t *newVal);
const wchar_t *CkJwtW_uncommonOptions(HCkJwtW cHandle);
This is a catch-all property to be used for uncommon needs. This property defaults to the empty string and should typically remain empty.
topVerboseLogging
void CkJwtW_putVerboseLogging(HCkJwtW cHandle, 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.
topVersion
const wchar_t *CkJwtW_version(HCkJwtW cHandle);
Methods
CreateJwt
const wchar_t *CkJwtW_createJwt(HCkJwtW cHandle, const wchar_t *header, const wchar_t *payload, const wchar_t *password);
Creates a JWT. The header is the JOSE JSON header. It can be the full JOSE JSON, or it can be a shorthand string such as "HS256", "HS384", or "HS512", in which case the standard JOSE header for the given algorithm will be used.
The payload is the JSON payload that contains the claims. The password is the secret. Given that the secret is a shared passwod string, this method should only be called for creating JWT's where the JOSE header's "alg" is HS256, HS384, or HS512. For RS256, RS384, RS512, ES256, ES384, and ES512, call CreateJwtPk instead.
When successful, this method returns a JWT with the format xxxxx.yyyyy.zzzzz, where xxxxx is the base64url encoded JOSE header, yyyyy is the base64url encoded payload, and zzzzz is the base64url signature.
Returns TRUE for success, FALSE for failure.
CreateJwtCert
const wchar_t *CkJwtW_createJwtCert(HCkJwtW cHandle, const wchar_t *header, const wchar_t *payload, HCkCertW cert);
Creates a JWT using a certificate's private key. The header is the JOSE JSON header. It can be the full JOSE JSON, or it can be a shorthand string such as "RS256", "RS384", "RS512", "PS256", "PS384", "PS512", "ES256", "ES384", or "ES512", in which case the standard JOSE header for the given algorithm will be used.
The payload is the JSON payload that contains the claims. The cert is the certificate with private key. This method should only be called for creating JWT's where the JOSE header's "alg" is RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, or ES512. If the secret is a shared password string, then call CreateJwt instead.
When successful, this method returns a JWT with the format xxxxx.yyyyy.zzzzz, where xxxxx is the base64url encoded JOSE header, yyyyy is the base64url encoded payload, and zzzzz is the base64url signature.
Note: Support for the PS256, PS384, PS512 algorithms was added in Chilkat v10.0.0.
Returns TRUE for success, FALSE for failure.
CreateJwtPk
const wchar_t *CkJwtW_createJwtPk(HCkJwtW cHandle, const wchar_t *header, const wchar_t *payload, HCkPrivateKeyW key);
Creates a JWT using an RSA or ECC private key. The header is the JOSE JSON header. It can be the full JOSE JSON, or it can be a shorthand string such as "RS256", "RS384", "RS512", "PS256", "PS384", "PS512", "ES256", "ES384", or "ES512", in which case the standard JOSE header for the given algorithm will be used.
The payload is the JSON payload that contains the claims. The key is the private key. This method should only be called for creating JWT's where the JOSE header's "alg" is RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, or ES512. If the secret is a shared password string, then call CreateJwt instead.
When successful, this method returns a JWT with the format xxxxx.yyyyy.zzzzz, where xxxxx is the base64url encoded JOSE header, yyyyy is the base64url encoded payload, and zzzzz is the base64url signature.
Note: Support for the PS256, PS384, PS512 algorithms was added in Chilkat v10.0.0.
Returns TRUE for success, FALSE for failure.
GenNumericDate
Generates a JSON numeric value representing the number of seconds from 1970-01-01T00:00:00Z UTC until the specified UTC date/time, ignoring leap seconds. The date/time generated is equal to the current system time plus the number of seconds specified by numSecOffset. The numSecOffset can be negative.
GetHeader
const wchar_t *CkJwtW_getHeader(HCkJwtW cHandle, const wchar_t *token);
Decodes the first part of a JWT (the "xxxxx" part of the "xxxxx.yyyyy.zzzzz" JWT) and returns the JSON string. This is the JOSE header of the JWT.
Returns TRUE for success, FALSE for failure.
GetPayload
const wchar_t *CkJwtW_getPayload(HCkJwtW cHandle, const wchar_t *token);
Decodes the second part of a JWT (the "yyyyy" part of the "xxxxx.yyyyy.zzzzz" JWT) and returns the JSON string. This is the claims payload of the JWT.
Returns TRUE for success, FALSE for failure.
IsTimeValid
Verifies the "exp" and/or "nbf" claims and returns TRUE if the current system date/time is within range. Returns FALSE if the current system date/time is outside the allowed range of time. The leeway may be set to a non-zero number of seconds to allow for some small leeway (usually no more than a few minutes) to account for clock skew.
VerifyJwt
Verifies a JWT that requires a shared password string for verification. The token should be a JWT with the format xxxxx.yyyyy.zzzzz. This method should only be called for JWT's using the HS256, HS384, or HS512 algorithms. The VerifyJwtPk method should be called for verifying JWT's requiring an RSA or ECC key.
Returns TRUE if the signature was verified. Returns FALSE if the signature was not successfully verified.
Note: This method will return FALSE if the "alg" in the JOSE header is anything other than the algorithms specifically for HMAC, namely "hs256, "hs384", and "hs512". For example, if the "alg" is "none", then this method immediately returns a failed status.
Further Explanation: This method calculates the signature using the password provided by the application, and compares it against the signature found in the JWT. If the signatures are equal, then the password is correct, and TRUE is returned.
Returns TRUE for success, FALSE for failure.
VerifyJwtPk
Verifies a JWT that requires an RSA or ECC public key for verification. The token should be a JWT with the format xxxxx.yyyyy.zzzzz. This method should only be called for JWT's using the RS256, RS384, RS512, ES256, ES384, or ES512 algorithms.
Returns TRUE if the signature was verified. Returns FALSE if the signature was not successfully verified.
Note: This method will return FALSE if the "alg" in the JOSE header is anything other than the algorithms specifically for RSA and ECC. For example, if the "alg" is "none", then this method immediately returns a failed status.
Further Explanation: This method calculates the signature using the key provided by the application, and compares it against the signature found in the JWT. If the signatures are equal, then the key corresponds to the private key used to sign, and TRUE is returned.
Returns TRUE for success, FALSE for failure.