# JWS Component

Create, Sign and Verify JSON Web Signatures (JWS).

## Syntax

```text
TipcJWS
```

## Remarks

The JWS component supports signing and verifying JSON Web Signatures (JWS).

Specify any payload via input properties and use [Sign](#sign-method-jws-component) to create a JWS message using a variety of algorithms including HMAC, RSA, and ECDSA. Use [Verify](#verify-method-jws-component) to verify the signature of any received JWS message. The following algorithms are supported:

- HS256
- HS384
- HS512
- RS256
- RS384
- RS512
- PS256
- PS384
- PS512
- ES256
- ES384
- ES512
- None

See [Algorithm](#algorithm-property-jws-component) for more details about supported algorithms.

## Signing

The [Sign](#sign-method-jws-component) method may be used to sign a payload with a variety of algorithms. Before calling the [Sign](#sign-method-jws-component) method set [Algorithm](#algorithm-property-jws-component) to the algorithm which will be used to sign the message. The result of signing is a compact serialized JWS string. For instance:

*eyJhbGciOiJIUzI1NiJ9.dGVzdA.o_JihJlCwvBO1AgY_Ao3_VBivdFmj3ufv3ZWAqYF4Ow*

The component is agnostic of the payload that is signed. Any value may be signed. [KeyId](#keyid-property-jws-component) may be set to include an identifier to help the receiving party identify the key used to sign the message. The following properties are applicable when calling this method:

- [Algorithm](#algorithm-property-jws-component) (required)
- [Certificate](#certificate-property-jws-component) (conditional - required for ECDSA and RSA)
- [Key](#key-property-jws-component) (conditional - required for HMAC)
- [HeaderParams](#headerparams-property-jws-component)
- [KeyId](#keyid-property-jws-component)
- [Overwrite](#overwrite-property-jws-component)

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

**Notes for HMAC Algorithms (HS256, HS384, HS512)**

When [Algorithm](#algorithm-property-jws-component) is set to a HMAC algorithm [Key](#key-property-jws-component) must be set to a key of appropriate length for the algorithm. The [Key](#key-property-jws-component) should be the same number of bits as the algorithm being used. For instance a 256 bit key would be used for HS256.

The example code below uses the [EzRand](EzRand.md#EzRand) component to generate a key, but the key may be created using any means. The key must be known by both parties in order for signing and verification to take place.

```csharp
//Generate a 256 bit (32 byte) key
Ezrand ezrand = new Ezrand();
ezrand.RandBytesLength = 32;
ezrand.GetNextBytes();
byte[] key = ezrand.RandBytesB;

//Sign the payload using HS256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsHS256;
jws.InputMessage = "test data";
jws.KeyB = key;
jws.Sign();

string signedData = jws.OutputMessage;
```

To use an existing HMAC key provide the bytes to the [Key](#key-property-jws-component) property. For instance:

```csharp
//HMAC SHA-256 Key
byte[] key = new byte[] { 170, 171, 221, 209, 7, 181, 48, 178, 48, 118, 242, 132, 36, 218, 74, 140, 216, 165, 161, 70, 11, 42, 246, 205, 235, 231, 19, 48, 87, 141, 122, 10 };

//Sign the payload using HS256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsHS256;
jws.InputMessage = "test data";
jws.KeyB = key;
jws.Sign();

string signedData = jws.OutputMessage;
```

**Notes for RSA Algorithms (RS256, RS384, RS512, PS256, PS384, PS512)**

The RSA based algorithms use asymmetric encryption. Signing is done with a private key and verification is done with a public key. The private key may be in PFX or PEM format.

```csharp
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsRS256;
jws.Certificate = new Certificate(CertStoreTypes.cstPFXFile, "..\\jwt.pfx", "test", "*");
jws.InputMessage = "test";
jws.Sign();

string signedMessage = jws.OutputMessage;
```

**Notes for ECDSA Algorithms (ES256, ES384, ES512)**

ECDSA algorithms require a valid ECC private key to sign. The [ECC](ECC.md#ECC) component can be used to create or import an ECC key into the *Certificate* format accepted by the *JWS* component.

```csharp
//Create an ECC key with SHA-256
Ecc ecc = new Ecc();
ecc.HashAlgorithm = EccHashAlgorithms.ehaSHA256;
ecc.CreateKey();

string privKey = ecc.Key.PrivateKey;

//Sign the payload using ES256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsES256;
jws.Certificate = new Certificate(CertStoreTypes.cstPEMKeyBlob, privKey, "", "*");
jws.InputMessage = "test";
jws.Sign();

string signedMessage = jws.OutputMessage;
```

To use an existing ECC Key populate the *Rx*, *Ry*, and *K* values of *Key* property in the [ECC](ECC.md#ECC) component first. For instance:

```csharp
//Import an existing ECC private key
Ecc ecc = new Ecc();

byte[] x_bytes = new byte[] { 171, 170, 196, 151, 94, 196, 231, 12, 128, 232, 17, 61, 45, 105, 41, 209, 192, 187, 112, 242, 110, 178, 95, 240, 36, 55, 83, 171, 190, 176, 78, 13 };
byte[] y_bytes = new byte[] { 197, 75, 134, 245, 245, 28, 199, 9, 7, 117, 1, 54, 49, 178, 135, 252, 62, 89, 35, 180, 117, 80, 231, 23, 110, 250, 28, 124, 219, 253, 224, 156 };
byte[] k_bytes = new byte[] { 81, 65, 201, 24, 235, 249, 162, 148, 169, 150, 109, 181, 61, 238, 145, 122, 31, 30, 151, 94, 239, 90, 222, 217, 63, 103, 54, 2, 176, 232, 248, 168 };

ecc.Key.RxB = x_bytes;
ecc.Key.RyB = y_bytes;
ecc.Key.KB = k_bytes;

string privKey = ecc.Key.PrivateKey;

//Sign the payload using ES256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsES256;
jws.Certificate = new Certificate(CertStoreTypes.cstPEMKeyBlob, privKey, "", "*");
jws.InputMessage = "test";
jws.Sign();

string signedMessage = jws.OutputMessage;
```

**Notes for Unsecured (none)**

To create a JWS token without any security set [Algorithm](#algorithm-property-jws-component) to *jwsNone*.

```csharp
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsNone;
jws.InputMessage = "test";
jws.Sign();

string unsecuredMessage = jws.OutputMessage;
```

## Signature Verification

The [Verify](#verify-method-jws-component) method may be used to verify a received JWS message. Before calling the [Verify](#verify-method-jws-component) method set [InputMessage](#inputmessage-property-jws-component) or [InputFile](#inputfile-property-jws-component) to a valid compact serialized JWS string. For instance:

*eyJhbGciOiJIUzI1NiJ9.dGVzdA.o_JihJlCwvBO1AgY_Ao3_VBivdFmj3ufv3ZWAqYF4Ow*

[Key](#key-property-jws-component) or [Certificate](#certificate-property-jws-component) should be set to the HMAC key or public certificate respectively. If the correct [Key](#key-property-jws-component) or [Certificate](#certificate-property-jws-component) is not known ahead of time the *KeyId* parameter of the [SignerInfo](#signerinfo-event-jws-component) event may be used to identify the correct key.

If this method returns without error verification was successful. If verification fails then this method raises an exception. After calling this method the payload will be present in the [OutputMessage](#outputmessage-property-jws-component) or file specified by [OutputFile](#outputfile-property-jws-component) and the [HeaderParams](#headerparams-property-jws-component) property will contain the headers. Headers of the parsed message are also available through the [HeaderParam](#headerparam-event-jws-component) event.

The following properties are applicable when calling this method:

- [Key](#key-property-jws-component) (conditional - required for HMAC)
- [Certificate](#certificate-property-jws-component) (conditional - required for ECDSA and RSA)
- [Algorithm](#algorithm-property-jws-component) (only if [StrictValidation](#StrictValidation) is True)
- [Overwrite](#overwrite-property-jws-component)
- [StrictValidation](#StrictValidation)

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

**Notes for HMAC Algorithms (HS256, HS384, HS512)**

When verifying a message originally signed with a HMAC algorithm [Key](#key-property-jws-component) must be set to the same key used during signing. The key must be known by both parties in order for signing and verification to take place.

```csharp
byte[] key = new byte[] { 170, 171, 221, 209, 7, 181, 48, 178, 48, 118, 242, 132, 36, 218, 74, 140, 216, 165, 161, 70, 11, 42, 246, 205, 235, 231, 19, 48, 87, 141, 122, 10 };

Jws jws = new Jws();
jws.KeyB = key;
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

**Notes for RSA Algorithms (RS256, RS384, RS512, PS256, PS384, PS512)**

The RSA based algorithms use asymmetric encryption. Signing is done with a private key and verification is done with a public key. The public key is typically in PEM format.

```csharp
Jws jws = new Jws();
jws.Certificate = new Certificate("..\\jwt.cer");
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

**Notes for ECDSA Algorithms (ES256, ES384, ES512)**

ECDSA algorithms require a valid ECC public key to verify the message. If the key was originally created with the [ECC](ECC.md#ECC) component the PEM encoded *PublicKey* may be used directly with the [Certificate](#certificate-property-jws-component) property. An example PEM encoded public certificate created by the [ECC](ECC.md#ECC) component:

```text
-----BEGIN PUBLIC KEY-----
MIIBMjCB7AYHKoZIzj0CATCB4AIBATAsBgcqhkjOPQEBAiEA/////wAAAAEAAAAAAAAAAAAA
AAD///////////////8wRAQg/////wAAAAEAAAAAAAAAAAAAAAD///////////////wEIFrG
NdiqOpPns+u9VXaYhrxlHQawzFOw9jvOPD4n0mBLBEEEaxfR8uEsQkf4vOblY6RA8ncDfYEt
6zOg9KE5RdiYwpZP40Li/hp/m47n60p8D54WK84zV2sxXs7LtkBoN79R9QIhAP////8AAAAA
//////////+85vqtpxeehPO5ysL8YyVRAgEBA0EEIC5rbLp11Mnz6cBXLLriaDIov3rm8RAY
x/OR0bOKiff0cQy+sLVaxjseqFk/+Xvl4ORSv5Z6HdHv5GyEpA0UoA==
-----END PUBLIC KEY-----
```

```csharp
Jws jws = new Jws();
jws.Certificate = new Certificate(CertStoreTypes.cstPublicKeyFile, pubKey, "", "*");
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

To use an ECC public key created by other means the [ECC](ECC.md#ECC) component may be used to import the key parameters. Populate the *Rx* and *Ry* of the [ECC](ECC.md#ECC) component first to obtain the PEM formatted public key. For instance:

```csharp
//Import an existing ECC public key
Ecc ecc = new Ecc();

byte[] x_bytes = new byte[] { 171, 170, 196, 151, 94, 196, 231, 12, 128, 232, 17, 61, 45, 105, 41, 209, 192, 187, 112, 242, 110, 178, 95, 240, 36, 55, 83, 171, 190, 176, 78, 13 };
byte[] y_bytes = new byte[] { 197, 75, 134, 245, 245, 28, 199, 9, 7, 117, 1, 54, 49, 178, 135, 252, 62, 89, 35, 180, 117, 80, 231, 23, 110, 250, 28, 124, 219, 253, 224, 156 };

ecc.Key.RxB = x_bytes;
ecc.Key.RyB = y_bytes;

string pubKey = ecc.Key.PublicKey;

Jws jws = new Jws();
jws.Certificate = new Certificate(CertStoreTypes.cstPublicKeyFile, pubKey, "", "*");
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

**Notes for Unsecured (none)**

To parse a JWS token without any security call the [Sign](#sign-method-jws-component) method without setting [Key](#key-property-jws-component) or [Certificate](#certificate-property-jws-component).

```csharp
Jws jws = new Jws();
jws.InputMessage = signedData;
jws.Verify();

string unsecuredPayload = jws.OutputMessage;
```

## Other Functionality

In addition to standard signing and verifying the component also supports a variety of other features including:

- Adding custom header parameters with [AddHeaderParam](#addheaderparam-method-jws-component)
- Enforcing algorithm restrictions when verifying by setting [StrictValidation](#StrictValidation)
- Inspect the JWS without verifying by calling [Parse](#parse-method-jws-component)

## Property List

*The following is the full list of the properties of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Algorithm](#algorithm-property-jws-component) | The algorithm used when signing. |
| [Certificate](#certificate-property-jws-component) | The certificate used for signing or verification. |
| [HeaderParams](#headerparams-property-jws-component) | The JOSE header parameters. |
| [InputFile](#inputfile-property-jws-component) | The file to process. |
| [InputMessage](#inputmessage-property-jws-component) | The message to process. |
| [Key](#key-property-jws-component) | The secret key for the hash algorithm. |
| [KeyId](#keyid-property-jws-component) | The Id of the key used to sign the message. |
| [OutputFile](#outputfile-property-jws-component) | The output file when encrypting or decrypting. |
| [OutputMessage](#outputmessage-property-jws-component) | The output message after processing. |
| [Overwrite](#overwrite-property-jws-component) | Indicates whether or not the component should overwrite files. |

## Method List

*The following is the full list of the methods of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [AddHeaderParam](#addheaderparam-method-jws-component) | Adds additional header parameters. |
| [Config](#config-method-jws-component) | Sets or retrieves a configuration setting. |
| [Parse](#parse-method-jws-component) | Parses the compact serialized JWS string. |
| [Reset](#reset-method-jws-component) | Resets the component. |
| [SetInputStream](#setinputstream-method-jws-component) | Sets the stream from which the component will read data. |
| [SetOutputStream](#setoutputstream-method-jws-component) | Sets the stream to which the component will write data. |
| [Sign](#sign-method-jws-component) | Signs the payload with the specified algorithm. |
| [Verify](#verify-method-jws-component) | Verifies the signature of the JWS token. |

## Event List

*The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Error](#error-event-jws-component) | Fired when information is available about errors during data delivery. |
| [HeaderParam](#headerparam-event-jws-component) | Fires once for each JOSE header parameter. |
| [SignerInfo](#signerinfo-event-jws-component) | Fires with information about the signature. |

## Config Settings

*The following is a list of config settings for the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [AllowedSigningAlgorithms](#AllowedSigningAlgorithms) | Allowed signing algorithms when StrictValidation is set to True. |
| [IncludeCertificateFormat](#IncludeCertificateFormat) | The certificate values to include in the signed message (if any). |
| [IssuerCerts](#IssuerCerts) | A collection of issuer certificates used with IncludeCertificateFormat. |
| [KeyEncoding](#KeyEncoding) | The encoding of the Key value. |
| [RawHeader](#RawHeader) | Holds the raw JOSE header. |
| [SerializationType](#SerializationType) | Determines the serialization type to use when reading and writing JWS content. |
| [StrictValidation](#StrictValidation) | Requires a specific algorithm when verifying signatures. |
| [BuildInfo](#BuildInfo) | Information about the product's build. |
| [CodePage](#CodePage) | The system code page used for Unicode to Multibyte translations. |
| [LicenseInfo](#LicenseInfo) | Information about the current license. |
| [MaskSensitiveData](#MaskSensitiveData) | Whether sensitive data is masked in log messages. |
| [UseFIPSCompliantAPI](#UseFIPSCompliantAPI) | Tells the component whether or not to use FIPS certified APIs. |
| [UseInternalSecurityAPI](#UseInternalSecurityAPI) | Whether or not to use the system security libraries or an internal implementation. |

# Algorithm Property ([JWS](#jws-component) Component)

The algorithm used when signing.

## Syntax

*Delphi Syntax*

```text
property Algorithm: TipcTJWSAlgorithms read get_Algorithm write set_Algorithm;
TipcTJWSAlgorithms = (
  jwsHS256,
  jwsHS384,
  jwsHS512,
  jwsRS256,
  jwsRS384,
  jwsRS512,
  jwsES256,
  jwsES384,
  jwsES512,
  jwsPS256,
  jwsPS384,
  jwsPS512,
  jwsES256K,
  jwsNone
);
```

## Default Value

jwsHS256

## Remarks

This property specifies the algorithm to use when signing.

When signing with an HMAC algorithm [Key](#key-property-jws-component) must be specified. When an RSA or ECDSA algorithm is selected [Certificate](#certificate-property-jws-component) must be set before calling [Sign](#sign-method-jws-component) and [Certificate](#certificate-property-jws-component) must be set before calling [Verify](#verify-method-jws-component). The following values are supported:

| Algorithm | Description | Private Key Location |
| --- | --- | --- |
| 0 (jwsHS256 - default) | HMAC using SHA-256 | [Key](#key-property-jws-component) |
| 1 (jwsHS384) | HMAC using SHA-384 | [Key](#key-property-jws-component) |
| 2 (jwsHS512) | HMAC using SHA-512 | [Key](#key-property-jws-component) |
| 3 (jwsRS256) | RSASSA-PKCS1-v1_5 using SHA-256 | [Certificate](#certificate-property-jws-component) |
| 4 (jwsRS384) | RSASSA-PKCS1-v1_5 using SHA-384 | [Certificate](#certificate-property-jws-component) |
| 5 (jwsRS512) | RSASSA-PKCS1-v1_5 using SHA-512 | [Certificate](#certificate-property-jws-component) |
| 6 (jwsPS256) | RSASSA-PSS using SHA-256 and MGF1 with SHA-256 | [Certificate](#certificate-property-jws-component) |
| 7 (jwsPS384) | RSASSA-PSS using SHA-384 and MGF1 with SHA-384 | [Certificate](#certificate-property-jws-component) |
| 8 (jwsPS512) | RSASSA-PSS using SHA-512 and MGF1 with SHA-512 | [Certificate](#certificate-property-jws-component) |
| 9 (jwsES256) | ECDSA using P-256 and SHA-256 | [Certificate](#certificate-property-jws-component) |
| 10 (jwsES384) | ECDSA using P-384 and SHA-384 | [Certificate](#certificate-property-jws-component) |
| 11 (jwsES512) | ECDSA using P-521 and SHA-512 | [Certificate](#certificate-property-jws-component) |
| 12 (jwsES256K) | ECDSA using secp256k1 curve and SHA-256 | [Certificate](#certificate-property-jws-component) |
| 99 (jwsNone) | None (unprotected) | Not Applicable |

Note: This setting is also applicable when [StrictValidation](#StrictValidation) is enabled before calling [Verify](#verify-method-jws-component).

# Certificate Property ([JWS](#jws-component) Component)

The certificate used for signing or verification.

## Syntax

*Delphi Syntax*

```text
property Certificate: TipcCertificate read get_Certificate write set_Certificate;
```

## Remarks

This property specifies a certificate used for signing or verification.

When calling [Sign](#sign-method-jws-component) and [Algorithm](#algorithm-property-jws-component) is set to an RSA or ECDSA algorithm this property must be set to a certificate with private key.

When calling [Verify](#verify-method-jws-component) and the algorithm used is RSA or ECDSA this property must be set to the public certificate of the signer.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# HeaderParams Property ([JWS](#jws-component) Component)

The JOSE header parameters.

## Syntax

*Delphi Syntax*

```text
property HeaderParams: TipcHeaderParamList read get_HeaderParams write set_HeaderParams;
```

## Remarks

This property specifies the JOSE header parameters. This may be populated before calling [Sign](#sign-method-jws-component) or Encrypt. This is populated with the parsed header values after calling [Verify](#verify-method-jws-component), Decrypt, or [Parse](#parse-method-jws-component).

This property is not available at design time.

 Please refer to the [HeaderParam](#headerparam-type) type for a complete list of fields.

# InputFile Property ([JWS](#jws-component) Component)

The file to process.

## Syntax

*Delphi Syntax*

```text
property InputFile: String read get_InputFile write set_InputFile;
```

## Default Value

''

## Remarks

This property specifies the file to be processed. Set this property to the full or relative path to the file which will be processed.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- InputFile
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# InputMessage Property ([JWS](#jws-component) Component)

The message to process.

## Syntax

*Delphi Syntax*

```text
property InputMessage: String read get_InputMessage write set_InputMessage;
property InputMessageB: TBytes read get_InputMessageB write set_InputMessageB;
```

## Default Value

''

## Remarks

This property specifies the message to be processed.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- InputMessage

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# Key Property ([JWS](#jws-component) Component)

The secret key for the hash algorithm.

## Syntax

*Delphi Syntax*

```text
property Key: String read get_Key write set_Key;
property KeyB: TBytes read get_KeyB write set_KeyB;
```

## Default Value

''

## Remarks

This property holds the secret key used when creating the hash. The key can be arbitrarily long.

Note: This property is only applicable when [Algorithm](#algorithm-property-jws-component) is set to an HMAC algorithm.

It is recommended that the length of the key be equal to or larger than the hash size of the algorithm. Use of keys shorter than the hash size is discouraged.

**Sizes (in bytes)**

|  |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- |
|  | SHA1 | SHA224 | SHA256 | SHA384 | SHA512 | MD5 | RIPEMD160 |
| Recommended Key Size | 20 | 28 | 32 | 48 | 64 | 16 | 20 |
| Hash Size | 20 | 28 | 32 | 48 | 64 | 16 | 20 |
| Block Size | 64 | 64 | 64 | 128 | 128 | 64 | 64 |

**Key Length Details**

As mentioned above it is recommended to use a key size equal to the hash size. Use of keys larger than the hash size does not typically significantly increase the function strength. Keys of any length are technically valid however see the below processing rules to understand how keys of varying lengths are treated:

- If the key length is equal to the hash size (recommended) it is used without modification.
- If the key length is less than the hash size it is used without modification.
- If the key length is less than or equal to the block size it is used without modification.
- If the key length is larger than the block size it is first hashed with the same algorithm.

# KeyId Property ([JWS](#jws-component) Component)

The Id of the key used to sign the message.

## Syntax

*Delphi Syntax*

```text
property KeyId: String read get_KeyId write set_KeyId;
```

## Default Value

''

## Remarks

This property optionally specifies the Id of the key used to sign the message.

Any string value may be supplied here to help the other party identify the key used to sign the message. This may be set before calling the [Sign](#sign-method-jws-component) method.

# OutputFile Property ([JWS](#jws-component) Component)

The output file when encrypting or decrypting.

## Syntax

*Delphi Syntax*

```text
property OutputFile: String read get_OutputFile write set_OutputFile;
```

## Default Value

''

## Remarks

This property specifies the file to which the output will be written when Encrypt or Decrypt is called. This may be set to an absolute or relative path.

This property is only applicable to Encrypt and Decrypt.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- OutputFile
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# OutputMessage Property ([JWS](#jws-component) Component)

The output message after processing.

## Syntax

*Delphi Syntax*

```text
property OutputMessage: String read get_OutputMessage;
property OutputMessageB: TBytes read get_OutputMessageB;
```

## Default Value

''

## Remarks

This property will be populated with the output from the operation if [OutputFile](#outputfile-property-jws-component) is not set.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- OutputMessage: The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

This property is read-only and not available at design time.

# Overwrite Property ([JWS](#jws-component) Component)

Indicates whether or not the component should overwrite files.

## Syntax

*Delphi Syntax*

```text
property Overwrite: Boolean read get_Overwrite write set_Overwrite;
```

## Default Value

false

## Remarks

This property indicates whether or not the component will overwrite [OutputFile](#outputfile-property-jws-component). If Overwrite is False, an error will be thrown whenever [OutputFile](#outputfile-property-jws-component) exists before an operation. The default value is False.

# AddHeaderParam Method ([JWS](#jws-component) Component)

Adds additional header parameters.

## Syntax

*Delphi Syntax*

```text
procedure AddHeaderParam(name: String; value: String; dataType: Integer);
```

## Remarks

This method is used to add additional header parameters before calling [Sign](#sign-method-jws-component).

The *Name* and *Value* parameters define the name and value of the parameter respectively. The *DataType* parameter specifies the JSON data type of the value. Possible values for *DataType* are:

- 0 (Object)
- 1 (Array)
- 2 (String)
- 3 (Number)
- 4 (Bool)
- 5 (Null)

 To add additional parameters to the JOSE header use this method. For instance to create this header:

```text
{
  "alg": "HS512",
  "crit": [
    "exp"
  ],
  "exp": 12345687,
  "kid": "myKeyId",
  "type": "JWT"
}
```

The following code can be used:

```csharp
jws.Algorithm = JwsAlgorithms.jwsHS512;
jws.KeyId = "myKeyId";
jws.KeyB = key;
jws.AddHeaderParam("type", "JWT", 2);
jws.AddHeaderParam("crit", "[\"exp\"]", 1);
jws.AddHeaderParam("exp", "12345687", 3);
jws.InputMessage = "test";
jws.Sign();
string signedData = jws.OutputMessage;
```

Note: when calling [Sign](#sign-method-jws-component) the component will automatically add some headers based on properties that are set.

**Parameters Automatically Set:**

| Header Param | Property |
| --- | --- |
| alg | [Algorithm](#algorithm-property-jws-component) |
| kid | [KeyId](#keyid-property-jws-component) |

# Config Method ([JWS](#jws-component) Component)

Sets or retrieves a configuration setting.

## Syntax

*Delphi Syntax*

```text
function Config(ConfigurationString: String): String;
```

## Remarks

Config is a generic method available in every component. It is used to set and retrieve [configuration settings](#config-settings-jws-component) for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the Config method.

To set a configuration setting named *PROPERTY*, you must call *Config("PROPERTY=VALUE")*, where *VALUE* is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a [configuration setting](#config-settings-jws-component), you must call *Config("PROPERTY")*. The value will be returned as a string.

# Parse Method ([JWS](#jws-component) Component)

Parses the compact serialized JWS string.

## Syntax

*Delphi Syntax*

```text
procedure Parse();
```

## Remarks

This method parses, but does not verify, the JWS string.

Take care when using this method as no signature verification is performed. This method may be helpful in cases where information about the signature is contained within the payload, or for any other reason where the signature is not important.

If verification is desired, use [Verify](#verify-method-jws-component) instead. It is not necessary to call this method before calling [Verify](#verify-method-jws-component). [Verify](#verify-method-jws-component) will both parse and verify the message.

When calling this method the headers and payload are parsed. The [HeaderParam](#headerparam-event-jws-component) and [SignerInfo](#signerinfo-event-jws-component) events will fire and the [HeaderParams](#headerparams-property-jws-component) property will be populated. The payload will be written to the specified output location.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# Reset Method ([JWS](#jws-component) Component)

Resets the component.

## Syntax

*Delphi Syntax*

```text
procedure Reset();
```

## Remarks

When called, the component will reset all of its properties to their default values.

# SetInputStream Method ([JWS](#jws-component) Component)

Sets the stream from which the component will read data.

## Syntax

*Delphi Syntax*

```text
procedure SetInputStream(InputStream: TStream);
```

## Remarks

This method may be used to set a stream from which data will be read.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- SetInputStream
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# SetOutputStream Method ([JWS](#jws-component) Component)

Sets the stream to which the component will write data.

## Syntax

*Delphi Syntax*

```text
procedure SetOutputStream(OutputStream: TStream);
```

## Remarks

This method may be used to specify a stream to which data will be written.

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- SetOutputStream
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

# Sign Method ([JWS](#jws-component) Component)

Signs the payload with the specified algorithm.

## Syntax

*Delphi Syntax*

```text
procedure Sign();
```

## Remarks

This method signs the input with the specified [Algorithm](#algorithm-property-jws-component).

Before calling the Sign method set [Algorithm](#algorithm-property-jws-component) to the algorithm which will be used to sign the message. The result of signing is a compact serialized JWS string. For instance:

*eyJhbGciOiJIUzI1NiJ9.dGVzdA.o_JihJlCwvBO1AgY_Ao3_VBivdFmj3ufv3ZWAqYF4Ow*

The component is agnostic of the payload that is signed. Any value may be signed. [KeyId](#keyid-property-jws-component) may be set to include an identifier to help the receiving party identify the key used to sign the message. The following properties are applicable when calling this method:

- [Algorithm](#algorithm-property-jws-component) (required)
- [Certificate](#certificate-property-jws-component) (conditional - required for ECDSA and RSA)
- [Key](#key-property-jws-component) (conditional - required for HMAC)
- [HeaderParams](#headerparams-property-jws-component)
- [KeyId](#keyid-property-jws-component)
- [Overwrite](#overwrite-property-jws-component)

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

**Notes for HMAC Algorithms (HS256, HS384, HS512)**

When [Algorithm](#algorithm-property-jws-component) is set to a HMAC algorithm [Key](#key-property-jws-component) must be set to a key of appropriate length for the algorithm. The [Key](#key-property-jws-component) should be the same number of bits as the algorithm being used. For instance a 256 bit key would be used for HS256.

The example code below uses the [EzRand](EzRand.md#EzRand) component to generate a key, but the key may be created using any means. The key must be known by both parties in order for signing and verification to take place.

```csharp
//Generate a 256 bit (32 byte) key
Ezrand ezrand = new Ezrand();
ezrand.RandBytesLength = 32;
ezrand.GetNextBytes();
byte[] key = ezrand.RandBytesB;

//Sign the payload using HS256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsHS256;
jws.InputMessage = "test data";
jws.KeyB = key;
jws.Sign();

string signedData = jws.OutputMessage;
```

To use an existing HMAC key provide the bytes to the [Key](#key-property-jws-component) property. For instance:

```csharp
//HMAC SHA-256 Key
byte[] key = new byte[] { 170, 171, 221, 209, 7, 181, 48, 178, 48, 118, 242, 132, 36, 218, 74, 140, 216, 165, 161, 70, 11, 42, 246, 205, 235, 231, 19, 48, 87, 141, 122, 10 };

//Sign the payload using HS256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsHS256;
jws.InputMessage = "test data";
jws.KeyB = key;
jws.Sign();

string signedData = jws.OutputMessage;
```

**Notes for RSA Algorithms (RS256, RS384, RS512, PS256, PS384, PS512)**

The RSA based algorithms use asymmetric encryption. Signing is done with a private key and verification is done with a public key. The private key may be in PFX or PEM format.

```csharp
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsRS256;
jws.Certificate = new Certificate(CertStoreTypes.cstPFXFile, "..\\jwt.pfx", "test", "*");
jws.InputMessage = "test";
jws.Sign();

string signedMessage = jws.OutputMessage;
```

**Notes for ECDSA Algorithms (ES256, ES384, ES512)**

ECDSA algorithms require a valid ECC private key to sign. The [ECC](ECC.md#ECC) component can be used to create or import an ECC key into the *Certificate* format accepted by the *JWS* component.

```csharp
//Create an ECC key with SHA-256
Ecc ecc = new Ecc();
ecc.HashAlgorithm = EccHashAlgorithms.ehaSHA256;
ecc.CreateKey();

string privKey = ecc.Key.PrivateKey;

//Sign the payload using ES256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsES256;
jws.Certificate = new Certificate(CertStoreTypes.cstPEMKeyBlob, privKey, "", "*");
jws.InputMessage = "test";
jws.Sign();

string signedMessage = jws.OutputMessage;
```

To use an existing ECC Key populate the *Rx*, *Ry*, and *K* values of *Key* property in the [ECC](ECC.md#ECC) component first. For instance:

```csharp
//Import an existing ECC private key
Ecc ecc = new Ecc();

byte[] x_bytes = new byte[] { 171, 170, 196, 151, 94, 196, 231, 12, 128, 232, 17, 61, 45, 105, 41, 209, 192, 187, 112, 242, 110, 178, 95, 240, 36, 55, 83, 171, 190, 176, 78, 13 };
byte[] y_bytes = new byte[] { 197, 75, 134, 245, 245, 28, 199, 9, 7, 117, 1, 54, 49, 178, 135, 252, 62, 89, 35, 180, 117, 80, 231, 23, 110, 250, 28, 124, 219, 253, 224, 156 };
byte[] k_bytes = new byte[] { 81, 65, 201, 24, 235, 249, 162, 148, 169, 150, 109, 181, 61, 238, 145, 122, 31, 30, 151, 94, 239, 90, 222, 217, 63, 103, 54, 2, 176, 232, 248, 168 };

ecc.Key.RxB = x_bytes;
ecc.Key.RyB = y_bytes;
ecc.Key.KB = k_bytes;

string privKey = ecc.Key.PrivateKey;

//Sign the payload using ES256
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsES256;
jws.Certificate = new Certificate(CertStoreTypes.cstPEMKeyBlob, privKey, "", "*");
jws.InputMessage = "test";
jws.Sign();

string signedMessage = jws.OutputMessage;
```

**Notes for Unsecured (none)**

To create a JWS token without any security set [Algorithm](#algorithm-property-jws-component) to *jwsNone*.

```csharp
Jws jws = new Jws();
jws.Algorithm = JwsAlgorithms.jwsNone;
jws.InputMessage = "test";
jws.Sign();

string unsecuredMessage = jws.OutputMessage;
```

# Verify Method ([JWS](#jws-component) Component)

Verifies the signature of the JWS token.

## Syntax

*Delphi Syntax*

```text
procedure Verify();
```

## Remarks

This method verifies the signature of the JWS token.

Before calling the Verify method set [InputMessage](#inputmessage-property-jws-component) or [InputFile](#inputfile-property-jws-component) to a valid compact serialized JWS string. For instance:

*eyJhbGciOiJIUzI1NiJ9.dGVzdA.o_JihJlCwvBO1AgY_Ao3_VBivdFmj3ufv3ZWAqYF4Ow*

[Key](#key-property-jws-component) or [Certificate](#certificate-property-jws-component) should be set to the HMAC key or public certificate respectively. If the correct [Key](#key-property-jws-component) or [Certificate](#certificate-property-jws-component) is not known ahead of time the *KeyId* parameter of the [SignerInfo](#signerinfo-event-jws-component) event may be used to identify the correct key.

If this method returns without error verification was successful. If verification fails then this method raises an exception. After calling this method the payload will be present in the [OutputMessage](#outputmessage-property-jws-component) or file specified by [OutputFile](#outputfile-property-jws-component) and the [HeaderParams](#headerparams-property-jws-component) property will contain the headers. Headers of the parsed message are also available through the [HeaderParam](#headerparam-event-jws-component) event.

The following properties are applicable when calling this method:

- [Key](#key-property-jws-component) (conditional - required for HMAC)
- [Certificate](#certificate-property-jws-component) (conditional - required for ECDSA and RSA)
- [Algorithm](#algorithm-property-jws-component) (only if [StrictValidation](#StrictValidation) is True)
- [Overwrite](#overwrite-property-jws-component)
- [StrictValidation](#StrictValidation)

**Input and Output Properties**

The component will determine the source and destination of the input and output based on which properties are set.

The order in which the input properties are checked is as follows:

- [SetInputStream](#setinputstream-method-jws-component)
- [InputFile](#inputfile-property-jws-component)
- [InputMessage](#inputmessage-property-jws-component)

When a valid source is found, the search stops. The order in which the output properties are checked is as follows:

- [SetOutputStream](#setoutputstream-method-jws-component)
- [OutputFile](#outputfile-property-jws-component)
- [OutputMessage](#outputmessage-property-jws-component): The output data is written to this property if no other destination is specified.

When using streams, you may need to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) or [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing).

**Notes for HMAC Algorithms (HS256, HS384, HS512)**

When verifying a message originally signed with a HMAC algorithm [Key](#key-property-jws-component) must be set to the same key used during signing. The key must be known by both parties in order for signing and verification to take place.

```csharp
byte[] key = new byte[] { 170, 171, 221, 209, 7, 181, 48, 178, 48, 118, 242, 132, 36, 218, 74, 140, 216, 165, 161, 70, 11, 42, 246, 205, 235, 231, 19, 48, 87, 141, 122, 10 };

Jws jws = new Jws();
jws.KeyB = key;
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

**Notes for RSA Algorithms (RS256, RS384, RS512, PS256, PS384, PS512)**

The RSA based algorithms use asymmetric encryption. Signing is done with a private key and verification is done with a public key. The public key is typically in PEM format.

```csharp
Jws jws = new Jws();
jws.Certificate = new Certificate("..\\jwt.cer");
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

**Notes for ECDSA Algorithms (ES256, ES384, ES512)**

ECDSA algorithms require a valid ECC public key to verify the message. If the key was originally created with the [ECC](ECC.md#ECC) component the PEM encoded *PublicKey* may be used directly with the [Certificate](#certificate-property-jws-component) property. An example PEM encoded public certificate created by the [ECC](ECC.md#ECC) component:

```text
-----BEGIN PUBLIC KEY-----
MIIBMjCB7AYHKoZIzj0CATCB4AIBATAsBgcqhkjOPQEBAiEA/////wAAAAEAAAAAAAAAAAAA
AAD///////////////8wRAQg/////wAAAAEAAAAAAAAAAAAAAAD///////////////wEIFrG
NdiqOpPns+u9VXaYhrxlHQawzFOw9jvOPD4n0mBLBEEEaxfR8uEsQkf4vOblY6RA8ncDfYEt
6zOg9KE5RdiYwpZP40Li/hp/m47n60p8D54WK84zV2sxXs7LtkBoN79R9QIhAP////8AAAAA
//////////+85vqtpxeehPO5ysL8YyVRAgEBA0EEIC5rbLp11Mnz6cBXLLriaDIov3rm8RAY
x/OR0bOKiff0cQy+sLVaxjseqFk/+Xvl4ORSv5Z6HdHv5GyEpA0UoA==
-----END PUBLIC KEY-----
```

```csharp
Jws jws = new Jws();
jws.Certificate = new Certificate(CertStoreTypes.cstPublicKeyFile, pubKey, "", "*");
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

To use an ECC public key created by other means the [ECC](ECC.md#ECC) component may be used to import the key parameters. Populate the *Rx* and *Ry* of the [ECC](ECC.md#ECC) component first to obtain the PEM formatted public key. For instance:

```csharp
//Import an existing ECC public key
Ecc ecc = new Ecc();

byte[] x_bytes = new byte[] { 171, 170, 196, 151, 94, 196, 231, 12, 128, 232, 17, 61, 45, 105, 41, 209, 192, 187, 112, 242, 110, 178, 95, 240, 36, 55, 83, 171, 190, 176, 78, 13 };
byte[] y_bytes = new byte[] { 197, 75, 134, 245, 245, 28, 199, 9, 7, 117, 1, 54, 49, 178, 135, 252, 62, 89, 35, 180, 117, 80, 231, 23, 110, 250, 28, 124, 219, 253, 224, 156 };

ecc.Key.RxB = x_bytes;
ecc.Key.RyB = y_bytes;

string pubKey = ecc.Key.PublicKey;

Jws jws = new Jws();
jws.Certificate = new Certificate(CertStoreTypes.cstPublicKeyFile, pubKey, "", "*");
jws.InputMessage = signedData;
jws.Verify();

string verifiedPayload = jws.OutputMessage;
```

**Notes for Unsecured (none)**

To parse a JWS token without any security call the [Sign](#sign-method-jws-component) method without setting [Key](#key-property-jws-component) or [Certificate](#certificate-property-jws-component).

```csharp
Jws jws = new Jws();
jws.InputMessage = signedData;
jws.Verify();

string unsecuredPayload = jws.OutputMessage;
```

# Error Event ([JWS](#jws-component) Component)

Fired when information is available about errors during data delivery.

## Syntax

*Delphi Syntax*

```text
type TErrorEvent = procedure (
  Sender: TObject;
  ErrorCode: Integer;
  const Description: String
) of Object;
property OnError: TErrorEvent read FOnError write FOnError;
```

## Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component raises an exception.

The *ErrorCode* parameter contains an error code, and the *Description* parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the [Error Codes](#trappable-errors-jws-component) section.

# HeaderParam Event ([JWS](#jws-component) Component)

Fires once for each JOSE header parameter.

## Syntax

*Delphi Syntax*

```text
type THeaderParamEvent = procedure (
  Sender: TObject;
  const Name: String;
  const Value: String;
  DataType: Integer
) of Object;
property OnHeaderParam: THeaderParamEvent read FOnHeaderParam write FOnHeaderParam;
```

## Remarks

When [Verify](#verify-method-jws-component) or [Parse](#parse-method-jws-component) is called this event will fire once for each JOSE header parameter.

*Name* is the name of the parameter.

*Value* is the value of the parameter.

*DataType* specifies the JSON data type of the value. Possible values are:

- 0 (Object)
- 1 (Array)
- 2 (String)
- 3 (Number)
- 4 (Bool)
- 5 (Null)

# SignerInfo Event ([JWS](#jws-component) Component)

Fires with information about the signature.

## Syntax

*Delphi Syntax*

```text
type TSignerInfoEvent = procedure (
  Sender: TObject;
  const KeyId: String;
  const Algorithm: String
) of Object;
property OnSignerInfo: TSignerInfoEvent read FOnSignerInfo write FOnSignerInfo;
```

## Remarks

This event fires with information about the signature. This may be used to help identify the [Key](#key-property-jws-component) or [Certificate](#certificate-property-jws-component) to load in order to verify the signature. This event fires when [Verify](#verify-method-jws-component) or [Parse](#parse-method-jws-component) is called.

*KeyId* is the Id of the key as supplied by the signer that created the message. This may be empty.

*Algorithm* is the signature algorithm used to sign the message.

# Certificate Type

This is the digital certificate being used.

## Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

The following fields are available:

- [EffectiveDate](#Certificate_f_EffectiveDate)

- [Encoded](#Certificate_f_Encoded)

- [ExpirationDate](#Certificate_f_ExpirationDate)

- [ExtendedKeyUsage](#Certificate_f_ExtendedKeyUsage)

- [Fingerprint](#Certificate_f_Fingerprint)

- [FingerprintSHA1](#Certificate_f_FingerprintSHA1)

- [FingerprintSHA256](#Certificate_f_FingerprintSHA256)

- [Issuer](#Certificate_f_Issuer)

- [PrivateKey](#Certificate_f_PrivateKey)

- [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable)

- [PrivateKeyContainer](#Certificate_f_PrivateKeyContainer)

- [PublicKey](#Certificate_f_PublicKey)

- [PublicKeyAlgorithm](#Certificate_f_PublicKeyAlgorithm)

- [PublicKeyLength](#Certificate_f_PublicKeyLength)

- [SerialNumber](#Certificate_f_SerialNumber)

- [SignatureAlgorithm](#Certificate_f_SignatureAlgorithm)

- [Store](#Certificate_f_Store)

- [StorePassword](#Certificate_f_StorePassword)

- [StoreType](#Certificate_f_StoreType)

- [Subject](#Certificate_f_Subject)

- [SubjectAltNames](#Certificate_f_SubjectAltNames)

- [ThumbprintMD5](#Certificate_f_ThumbprintMD5)

- [ThumbprintSHA1](#Certificate_f_ThumbprintSHA1)

- [ThumbprintSHA256](#Certificate_f_ThumbprintSHA256)

- [Usage](#Certificate_f_Usage)

- [UsageFlags](#Certificate_f_UsageFlags)

- [Version](#Certificate_f_Version)

## Fields

 **EffectiveDate** *String (read-only)*
*Default Value: ""*

The date on which this certificate becomes valid. Before this date, it is not valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:

23-Jan-2000 15:00:00.

 **Encoded** *String*
*Default Value: ""*

The certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) properties also may be used to specify a certificate.

When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string.

 **EncodedB** *TBytes*
*Default Value: ""*

The certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) properties also may be used to specify a certificate.

When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string.

 **ExpirationDate** *String (read-only)*
*Default Value: ""*

The date on which the certificate expires. After this date, the certificate will no longer be valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:

23-Jan-2001 15:00:00.

 **ExtendedKeyUsage** *String (read-only)*
*Default Value: ""*

A comma-delimited list of extended key usage identifiers. These are the same as ASN.1 object identifiers (OIDs).

 **Fingerprint** *String (read-only)*
*Default Value: ""*

The hex-encoded, 16-byte MD5 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *bc:2a:72:af:fe:58:17:43:7a:5f:ba:5a:7c:90:f7:02*

 **FingerprintSHA1** *String (read-only)*
*Default Value: ""*

The hex-encoded, 20-byte SHA-1 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *30:7b:fa:38:65:83:ff:da:b4:4e:07:3f:17:b8:a4:ed:80:be:ff:84*

 **FingerprintSHA256** *String (read-only)*
*Default Value: ""*

The hex-encoded, 32-byte SHA-256 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *6a:80:5c:33:a9:43:ea:b0:96:12:8a:64:96:30:ef:4a:8a:96:86:ce:f4:c7:be:10:24:8e:2b:60:9e:f3:59:53*

 **Issuer** *String (read-only)*
*Default Value: ""*

The issuer of the certificate. This property contains a string representation of the name of the issuing authority for the certificate.

 **PrivateKey** *String (read-only)*
*Default Value: ""*

The private key of the certificate (if available). The key is provided as PEM/Base64-encoded data.

NOTE: The [PrivateKey](#Certificate_f_PrivateKey) may be available but not exportable. In this case, [PrivateKey](#Certificate_f_PrivateKey) returns an empty string.

 **PrivateKeyAvailable** *Boolean (read-only)*
*Default Value: False*

Whether a [PrivateKey](#Certificate_f_PrivateKey) is available for the selected certificate. If [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable) is True, the certificate may be used for authentication purposes (e.g., server authentication).

 **PrivateKeyContainer** *String (read-only)*
*Default Value: ""*

The name of the [PrivateKey](#Certificate_f_PrivateKey) container for the certificate (if available). This functionality is available only on Windows platforms.

 **PublicKey** *String (read-only)*
*Default Value: ""*

The public key of the certificate. The key is provided as PEM/Base64-encoded data.

 **PublicKeyAlgorithm** *String (read-only)*
*Default Value: ""*

The textual description of the certificate's public key algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_DH") or an object identifier (OID) string representing the algorithm.

 **PublicKeyLength** *Integer (read-only)*
*Default Value: 0*

The length of the certificate's public key (in bits). Common values are 512, 1024, and 2048.

 **SerialNumber** *String (read-only)*
*Default Value: ""*

The serial number of the certificate encoded as a string. The number is encoded as a series of hexadecimal digits, with each pair representing a byte of the serial number.

 **SignatureAlgorithm** *String (read-only)*
*Default Value: ""*

The text description of the certificate's signature algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_MD5RSA") or an object identifier (OID) string representing the algorithm.

 **Store** *String*
*Default Value: "MY"*

The name of the certificate store for the client certificate.

The [StoreType](#Certificate_f_StoreType) property denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword).

[Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) property to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) property for details.

 Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

|  |  |
| --- | --- |
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |

When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

 **StoreB** *TBytes*
*Default Value: "MY"*

The name of the certificate store for the client certificate.

The [StoreType](#Certificate_f_StoreType) property denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword).

[Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) property to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) property for details.

 Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

|  |  |
| --- | --- |
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |

When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

 **StorePassword** *String*
*Default Value: ""*

If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.

 **StoreType** *TipcCertStoreTypes*
*Default Value: 0*

The type of certificate store for this certificate.

 The component supports both public and private keys in a variety of formats. When the *cstAuto* value is used, the component will automatically determine the type. This property can take one of the following values:

```csharp
sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11,
                               @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll",
                               "123456", // PIN
                               "CN=cert_subject");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

```csharp
certmgr.CertStoreType = CertStoreTypes.cstPKCS11;
certmgr.OnCertList += (s, e) => {
  secKeyBlob = e.CertEncoded;
};
certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll";
certmgr.CertStorePassword = "123456"; // PIN
certmgr.ListStoreCertificates();

sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

|  |  |
| --- | --- |
| 0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user. NOTE: This store type is not available in Java. |
| 1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store. NOTE: This store type is not available in Java. |
| 2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
| 3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
| 4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates. NOTE: This store type is only available in Java. |
| 5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. NOTE: This store type is only available in Java. |
| 6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
| 7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
| 8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
| 9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
| 10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
| 11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
| 12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
| 13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
| 14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
| 15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
| 16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
| 17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
| 18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
| 19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
| 21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). NOTE: This store type is only available in Java and .NET. |
| 22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. NOTE: This store type is only available in Java and .NET. |
| 23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface. To use a security key, create a new [Certificate](#certificate-type) object and pass cstPKCS11 as the [StoreType](#Certificate_f_StoreType), the full path of the PKCS#11 DLL as the [Store](#Certificate_f_Store), and the PIN as the [StorePassword](#Certificate_f_StorePassword). Code Example. SSH Authentication with Security Key (without CertMgr): Alternatively, collect the necessary data using the [CertMgr](CertMgr.md#CertMgr) component by calling the [ListStoreCertificates](CertMgr.md#CertMgr_m_ListStoreCertificates) method after setting the corresponding properties accordingly. The certificate information returned in the [CertList](CertMgr.md#CertMgr_e_CertList) event's CertEncoded parameter may be saved for later use. When using a certificate obtained with this approach, pass the previously saved security key information as the [Store](#Certificate_f_Store) and set [StorePassword](#Certificate_f_StorePassword) to the PIN. Code Example. SSH Authentication with Security Key (with CertMgr): |
| 99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |

 **Subject** *String*
*Default Value: ""*

The subject of the certificate used for client authentication.

This property must be set after all other certificate properties are set. When this property is set, a search is performed in the current certificate store to locate a certificate with a matching subject.

If a matching certificate is found, the property is set to the full subject of the matching certificate.

If an exact match is not found, the store is searched for subjects containing the value of the property.

If a match is still not found, the property is set to an empty string, and no certificate is selected.

The special value "*" picks a random certificate in the certificate store.

The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=example@email.com". Common fields and their meanings are as follows:

| Field | Meaning |
| --- | --- |
| CN | Common Name. This is commonly a hostname like www.server.com. |
| O | Organization |
| OU | Organizational Unit |
| L | Locality |
| S | State |
| C | Country |
| E | Email Address |

If a field value contains a comma, it must be quoted.

 **SubjectAltNames** *String (read-only)*
*Default Value: ""*

Comma-separated lists of alternative subject names for the certificate.

 **ThumbprintMD5** *String (read-only)*
*Default Value: ""*

The MD5 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **ThumbprintSHA1** *String (read-only)*
*Default Value: ""*

The SHA-1 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **ThumbprintSHA256** *String (read-only)*
*Default Value: ""*

The SHA-256 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **Usage** *String (read-only)*
*Default Value: ""*

The text description of [UsageFlags](#Certificate_f_UsageFlags).

This value will be one or more of the following strings and will be separated by commas:

- Digital Signature
- Non-Repudiation
- Key Encipherment
- Data Encipherment
- Key Agreement
- Certificate Signing
- CRL Signing
- Encipher Only

If the provider is OpenSSL, the value is a comma-separated list of X.509 certificate extension names.

 **UsageFlags** *Integer (read-only)*
*Default Value: 0*

The flags that show intended use for the certificate. The value of [UsageFlags](#Certificate_f_UsageFlags) is a combination of the following flags:

|  |  |
| --- | --- |
| 0x80 | Digital Signature |
| 0x40 | Non-Repudiation |
| 0x20 | Key Encipherment |
| 0x10 | Data Encipherment |
| 0x08 | Key Agreement |
| 0x04 | Certificate Signing |
| 0x02 | CRL Signing |
| 0x01 | Encipher Only |

Please see the [Usage](#Certificate_f_Usage) property for a text representation of [UsageFlags](#Certificate_f_UsageFlags).

This functionality currently is not available when the provider is OpenSSL.

 **Version** *String (read-only)*
*Default Value: ""*

The certificate's version number. The possible values are the strings "V1", "V2", and "V3".

## Constructors

 >

*Delphi Syntax*

```text
constructor Create();
```

 Creates a instance whose properties can be set.

 >

*Delphi Syntax*

```text
constructor Create(valEncoded: TBytes);
```

 Parses * Encoded * as an X.509 public key.

 >

*Delphi Syntax*

```text
constructor Create(valStoreType: TipcCertStoreTypes; valStore: String; valStorePassword: String; valSubject: String);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

 >

*Delphi Syntax*

```text
constructor Create(valStoreType: TipcCertStoreTypes; valStore: TBytes; valStorePassword: String; valSubject: String);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

# HeaderParam Type

The JOSE header parameter.

## Remarks

This type holds the JOSE header parameters. The fields define the name, value, and data type of the parameter.

The following fields are available:

- [DataType](#HeaderParam_f_DataType)

- [Name](#HeaderParam_f_Name)

- [Value](#HeaderParam_f_Value)

## Fields

 **DataType** *TipcTDataTypes*
*Default Value: 2*

The data type of the header parameter.

This property specifies the JSON type of the header parameter value. Possible values are:

- 0 (Object)
- 1 (Array)
- 2 (String)
- 3 (Number)
- 4 (Bool)
- 5 (Null)

 **Name** *String*
*Default Value: ""*

The header parameter name.

 **Value** *String*
*Default Value: ""*

The header parameter value.

## Constructors

 >

*Delphi Syntax*

```text
constructor Create();
```

 Creates a new header parameter with no name or value.

 >

*Delphi Syntax*

```text
constructor Create(valName: String; valValue: String);
```

 Creates a new header parameter. The DataType of the value will be a String.

# Config Settings ([JWS](#jws-component) Component)

 The component accepts one or more of the following *configuration settings*. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the [Config](#config-method-jws-component) method.

### JWS Config Settings

**AllowedSigningAlgorithms**: Allowed signing algorithms when StrictValidation is set to True.This setting specifics a comma separated list of algorithms that are allowed when [StrictValidation](#StrictValidation) is set to *True*. This allows multiple signing algorithms to be considered acceptable during validation. This setting is only applicable when [StrictValidation](#StrictValidation) is set to *True*. Possible values:

- *HS256*
- *HS384*
- *HS512*
- *RS256*
- *RS384*
- *RS512*
- *ES256*
- *ES384*
- *ES512*
- *PS256*
- *PS384*
- *PS512*

Example value: *HS512,HS256*.

**IncludeCertificateFormat**: The certificate values to include in the signed message (if any).This setting specifies whether information about the [Certificate](#certificate-property-jws-component) is included in the signed message. When specified, the value here determines the format of the included certificate information. The certificate information is included as a standard JWS header parameter.

Multiple formats may be included in the signed message. The value specified should be the binary 'OR' of one or more of the following values:

| Value | Description | JWS Header Param |
| --- | --- | --- |
| 0 (0x00 - default) | None |  |
| 1 (0x01) | X.509 Certificate Chain | x5c |
| 2 (0x02) | X.509 Certificate SHA-1 Thumbprint (Base64-URL encoded) | x5t |
| 4 (0x04) | X.509 Certificate SHA-256 Thumbprint (Base64-URL encoded) | x5t#S256 |

Note: When including the certificate chain (*0x01*) the public certificate of [Certificate](#certificate-property-jws-component) property will automatically be included. [IssuerCerts](#IssuerCerts) may also be set to the public issuer certificates that will be used when building the chain to include.

For instance, to include both the certificate chain and SHA-256 thumbprint of the [Certificate](#certificate-property-jws-component) set this to *5*.

**IssuerCerts**: A collection of issuer certificates used with IncludeCertificateFormat.This setting optionally specifies one or more issuer certificates that may be used by the component when [IncludeCertificateFormat](#IncludeCertificateFormat) is specified. Note that the issuer certificates specified here are used as a store of potential issuer certificates. At runtime the component will inspect the [Certificate](#certificate-property-jws-component) value and add the relevant issuer certificates that are present in this property.

The format of the value must be one or more PEM encoded certificates with headers and footers. For instance to include 2 issuer certificates the value may be:

```text
-----BEGIN CERTIFICATE-----
MIIBujCCASOgAwIBAgICA+kwDQYJKoZIhvcNAQELBQAwHTEbMBkGA1UEAxMSbnVuaXRDZXJ0
Q2hhaW5Sb290MCAXDTE4MTAxNTA5MDAxN1oYDzIxMTgwOTIxMDkwMDE3WjAmMSQwIgYDVQQD
...
Tr+wi0ouNo7ifWRcE83Z15PhfGn1nkfxMYj4rya5n+V0RVVcgFUdiolCI5o/sYq503a7kH16
JSF5Zw+TiMz/COM8R94=
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIBsTCCARqgAwIBAgICA+gwDQYJKoZIhvcNAQELBQAwHTEbMBkGA1UEAxMSbnVuaXRDZXJ0
Q2hhaW5Sb290MCAXDTE4MTAxNTA5MDAxN1oYDzIxMTgwOTIxMDkwMDE3WjAdMRswGQYDVQQD
...
5u2K9PuJ3ySgL7AvYsqbB/e0/gw8j253SOU+gNTpFahOJsLGEJ43CRtaowkLnWEzs+OPnRfw
iQmqruw=
-----END CERTIFICATE-----
```

**KeyEncoding**: The encoding of the Key value.This setting specifies the encoding that has been applied to the [Key](#key-property-jws-component). value prior to providing it to the component. The [Key](#key-property-jws-component) is typically represented as an array of bytes, however in some cases the key value may have been encoded. As a matter of convenience the component will accept the key with an encoding already applied. The component will decode the key value according the to the value specified here before processing. Possible values are:

- 0 (none - default)
- 1 (Base64)
- 2 (Hex)
- 3 (Base64URL)

**RawHeader**: Holds the raw JOSE header.This setting may be queried after calling [Sign](#sign-method-jws-component) or [Verify](#verify-method-jws-component) to obtain the raw JOSE header. This returns a JSON string like:

*{"alg":"ES384","kid":"myKeyId"}*

**SerializationType**: Determines the serialization type to use when reading and writing JWS content.This setting is used to control the serialization type the component uses when reading and writing JWS content. Possible values are:

- *0* *(default)*: Compact serialization (content is serialized as a single base64url-encoded string).
- *1*: Standard JSON serialization.
- *2*: Flattened JSON serialization.

**StrictValidation**: Requires a specific algorithm when verifying signatures.If set to True the component will validate that the Algorithm in the JWS message matches the value specified in the [Algorithm](#algorithm-property-jws-component) property. If it does not an error is thrown. By default this is False and the algorithm is read and used automatically from the message. Enabling this setting provides a way to require a specific algorithm when calling VerifySignature.

### Base Config Settings

**BuildInfo**: Information about the product's build.When queried, this setting will return a string containing information about the product's build.

**CodePage**: The system code page used for Unicode to Multibyte translations.The default code page is Unicode UTF-8 (65001).

The following is a list of valid code page identifiers:

|  |  |
| --- | --- |
| Identifier | Name |
| 037 | IBM EBCDIC - U.S./Canada |
| 437 | OEM - United States |
| 500 | IBM EBCDIC - International |
| 708 | Arabic - ASMO 708 |
| 709 | Arabic - ASMO 449+, BCON V4 |
| 710 | Arabic - Transparent Arabic |
| 720 | Arabic - Transparent ASMO |
| 737 | OEM - Greek (formerly 437G) |
| 775 | OEM - Baltic |
| 850 | OEM - Multilingual Latin I |
| 852 | OEM - Latin II |
| 855 | OEM - Cyrillic (primarily Russian) |
| 857 | OEM - Turkish |
| 858 | OEM - Multilingual Latin I + Euro symbol |
| 860 | OEM - Portuguese |
| 861 | OEM - Icelandic |
| 862 | OEM - Hebrew |
| 863 | OEM - Canadian-French |
| 864 | OEM - Arabic |
| 865 | OEM - Nordic |
| 866 | OEM - Russian |
| 869 | OEM - Modern Greek |
| 870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
| 874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
| 875 | IBM EBCDIC - Modern Greek |
| 932 | ANSI/OEM - Japanese, Shift-JIS |
| 936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
| 949 | ANSI/OEM - Korean (Unified Hangul Code) |
| 950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
| 1026 | IBM EBCDIC - Turkish (Latin-5) |
| 1047 | IBM EBCDIC - Latin 1/Open System |
| 1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
| 1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
| 1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
| 1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
| 1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
| 1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
| 1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
| 1147 | IBM EBCDIC - France (20297 + Euro symbol) |
| 1148 | IBM EBCDIC - International (500 + Euro symbol) |
| 1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
| 1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
| 1201 | Unicode UCS-2 Big-Endian |
| 1250 | ANSI - Central European |
| 1251 | ANSI - Cyrillic |
| 1252 | ANSI - Latin I |
| 1253 | ANSI - Greek |
| 1254 | ANSI - Turkish |
| 1255 | ANSI - Hebrew |
| 1256 | ANSI - Arabic |
| 1257 | ANSI - Baltic |
| 1258 | ANSI/OEM - Vietnamese |
| 1361 | Korean (Johab) |
| 10000 | MAC - Roman |
| 10001 | MAC - Japanese |
| 10002 | MAC - Traditional Chinese (Big5) |
| 10003 | MAC - Korean |
| 10004 | MAC - Arabic |
| 10005 | MAC - Hebrew |
| 10006 | MAC - Greek I |
| 10007 | MAC - Cyrillic |
| 10008 | MAC - Simplified Chinese (GB 2312) |
| 10010 | MAC - Romania |
| 10017 | MAC - Ukraine |
| 10021 | MAC - Thai |
| 10029 | MAC - Latin II |
| 10079 | MAC - Icelandic |
| 10081 | MAC - Turkish |
| 10082 | MAC - Croatia |
| 12000 | Unicode UCS-4 Little-Endian |
| 12001 | Unicode UCS-4 Big-Endian |
| 20000 | CNS - Taiwan |
| 20001 | TCA - Taiwan |
| 20002 | Eten - Taiwan |
| 20003 | IBM5550 - Taiwan |
| 20004 | TeleText - Taiwan |
| 20005 | Wang - Taiwan |
| 20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
| 20106 | IA5 German (7-bit) |
| 20107 | IA5 Swedish (7-bit) |
| 20108 | IA5 Norwegian (7-bit) |
| 20127 | US-ASCII (7-bit) |
| 20261 | T.61 |
| 20269 | ISO 6937 Non-Spacing Accent |
| 20273 | IBM EBCDIC - Germany |
| 20277 | IBM EBCDIC - Denmark/Norway |
| 20278 | IBM EBCDIC - Finland/Sweden |
| 20280 | IBM EBCDIC - Italy |
| 20284 | IBM EBCDIC - Latin America/Spain |
| 20285 | IBM EBCDIC - United Kingdom |
| 20290 | IBM EBCDIC - Japanese Katakana Extended |
| 20297 | IBM EBCDIC - France |
| 20420 | IBM EBCDIC - Arabic |
| 20423 | IBM EBCDIC - Greek |
| 20424 | IBM EBCDIC - Hebrew |
| 20833 | IBM EBCDIC - Korean Extended |
| 20838 | IBM EBCDIC - Thai |
| 20866 | Russian - KOI8-R |
| 20871 | IBM EBCDIC - Icelandic |
| 20880 | IBM EBCDIC - Cyrillic (Russian) |
| 20905 | IBM EBCDIC - Turkish |
| 20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
| 20932 | JIS X 0208-1990 & 0121-1990 |
| 20936 | Simplified Chinese (GB2312) |
| 21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
| 21027 | Extended Alpha Lowercase |
| 21866 | Ukrainian (KOI8-U) |
| 28591 | ISO 8859-1 Latin I |
| 28592 | ISO 8859-2 Central Europe |
| 28593 | ISO 8859-3 Latin 3 |
| 28594 | ISO 8859-4 Baltic |
| 28595 | ISO 8859-5 Cyrillic |
| 28596 | ISO 8859-6 Arabic |
| 28597 | ISO 8859-7 Greek |
| 28598 | ISO 8859-8 Hebrew |
| 28599 | ISO 8859-9 Latin 5 |
| 28605 | ISO 8859-15 Latin 9 |
| 29001 | Europa 3 |
| 38598 | ISO 8859-8 Hebrew |
| 50220 | ISO 2022 Japanese with no halfwidth Katakana |
| 50221 | ISO 2022 Japanese with halfwidth Katakana |
| 50222 | ISO 2022 Japanese JIS X 0201-1989 |
| 50225 | ISO 2022 Korean |
| 50227 | ISO 2022 Simplified Chinese |
| 50229 | ISO 2022 Traditional Chinese |
| 50930 | Japanese (Katakana) Extended |
| 50931 | US/Canada and Japanese |
| 50933 | Korean Extended and Korean |
| 50935 | Simplified Chinese Extended and Simplified Chinese |
| 50936 | Simplified Chinese |
| 50937 | US/Canada and Traditional Chinese |
| 50939 | Japanese (Latin) Extended and Japanese |
| 51932 | EUC - Japanese |
| 51936 | EUC - Simplified Chinese |
| 51949 | EUC - Korean |
| 51950 | EUC - Traditional Chinese |
| 52936 | HZ-GB2312 Simplified Chinese |
| 54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
| 57002 | ISCII Devanagari |
| 57003 | ISCII Bengali |
| 57004 | ISCII Tamil |
| 57005 | ISCII Telugu |
| 57006 | ISCII Assamese |
| 57007 | ISCII Oriya |
| 57008 | ISCII Kannada |
| 57009 | ISCII Malayalam |
| 57010 | ISCII Gujarati |
| 57011 | ISCII Punjabi |
| 65000 | Unicode UTF-7 |
| 65001 | Unicode UTF-8 |

 The following is a list of valid code page identifiers for Mac OS only:

|  |  |
| --- | --- |
| Identifier | Name |
| 1 | ASCII |
| 2 | NEXTSTEP |
| 3 | JapaneseEUC |
| 4 | UTF8 |
| 5 | ISOLatin1 |
| 6 | Symbol |
| 7 | NonLossyASCII |
| 8 | ShiftJIS |
| 9 | ISOLatin2 |
| 10 | Unicode |
| 11 | WindowsCP1251 |
| 12 | WindowsCP1252 |
| 13 | WindowsCP1253 |
| 14 | WindowsCP1254 |
| 15 | WindowsCP1250 |
| 21 | ISO2022JP |
| 30 | MacOSRoman |
| 10 | UTF16String |
| 0x90000100 | UTF16BigEndian |
| 0x94000100 | UTF16LittleEndian |
| 0x8c000100 | UTF32String |
| 0x98000100 | UTF32BigEndian |
| 0x9c000100 | UTF32LittleEndian |
| 65536 | Proprietary |

**LicenseInfo**: Information about the current license.When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.

**MaskSensitiveData**: Whether sensitive data is masked in log messages.In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to *True* to mask sensitive data. The default is *True*.

**UseFIPSCompliantAPI**: Tells the component whether or not to use FIPS certified APIs.When set to *True*, the component will utilize the underlying operating system's certified APIs. Java editions, regardless of OS, utilize Bouncy Castle Federal Information Processing Standards (FIPS), while all other Windows editions make use of Microsoft security libraries.

FIPS mode can be enabled by setting the *UseFIPSCompliantAPI* configuration setting to *True*. This is a static setting that applies to all instances of all components of the toolkit within the process. It is recommended to enable or disable this setting once before the component has been used to establish a connection. Enabling FIPS while an instance of the component is active and connected may result in unexpected behavior.

For more details, please see the [FIPS 140-2 Compliance](https://www.nsoftware.com/kb/articles/fips.rst) article.

NOTE: This setting is applicable only on Windows.

NOTE: Enabling FIPS compliance requires a special license; please contact [sales@nsoftware.com](mailto:sales@nsoftware.com) for details.

**UseInternalSecurityAPI**: Whether or not to use the system security libraries or an internal implementation. When set to *False*, the component will use the system security libraries by default to perform cryptographic functions where applicable.

Setting this configuration setting to *True* tells the component to use the internal implementation instead of using the system security libraries.

 This setting is set to *False* by default on all platforms.

# Trappable Errors ([JWS](#jws-component) Component)

### JWS Errors

|  |  |
| --- | --- |
| 201 | Invalid JWS value. Not recognized as a compact serialized JWS string. |
| 202 | Signature verification failed. |
| 203 | Key must be specified before attempting this operation. |
| 204 | The specified key is too short for the selected algorithm. |
| 205 | Certificate must be specified before attempting this operation. |
| 206 | Unsupported algorithm. |
| 207 | OutputFile already exists and Overwrite is False. |
| 208 | Error writing data. See error message for details. |