---
product: Chilkat
product_version: 11.7.0
language: sqlserver
language_label: SQL Server
class: Rsa
license: bundle
deprecated: false
reference_html: https://www.chilkatsoft.com/refdoc/sqlserver_RsaRef.html
---
# Chilkat Rsa — SQL Server — v11.7.0

> Chilkat 11.7.0 · language=sqlserver · class=Rsa
> Other versions: replace `11.7.0` in this URL. Other languages: `https://www.chilkatsoft.com/ai-docs/v/11.7.0/<lang>/classes/Rsa.md`.
> Language-wide rules (install, unlock, error model, strings/bytes): `https://www.chilkatsoft.com/ai-docs/v/11.7.0/sqlserver/guide.md`.

## Purpose

**Encrypt, decrypt, sign, verify, and generate RSA keys.**

Use `Chilkat.Rsa` when an application needs direct RSA cryptographic operations. It can encrypt data with a public key, decrypt with a private key, create RSA signatures, verify signatures, sign precomputed hashes, verify signed hashes, and generate RSA key pairs. It also works with keys supplied directly as `PrivateKey` or `PublicKey` objects, or indirectly through certificates.

**RSA encryption**

Encrypt data with a public key for workflows where only the matching private key should be able to decrypt the result.

**RSA decryption**

Decrypt RSA-encrypted data using a private key, including keys loaded directly or accessed through a certificate.

**Sign and verify data**

Create and verify RSA signatures over data using the hash algorithm and padding mode required by the application or protocol.

**Sign precomputed hashes**

Sign or verify already-computed message digests when the hashing step is performed separately or by another component.

**Generate RSA keys**

Generate RSA key pairs for applications that need new public/private key material.

**Certificate-backed keys**

Use RSA keys associated with certificates, including non-exportable private keys in smart cards, USB tokens, Windows stores, or Apple Keychain.

**Common pattern:** Load or generate the RSA key material, configure the padding, hash, charset, and encoding options needed by the protocol, then call the method matching the operation: encrypt, decrypt, sign, verify, sign-hash, or verify-hash. Use `Chilkat.Rsa` for direct RSA operations; use higher-level classes such as `Crypt2`, `Jws`, `Jwt`, or `Mime` when the RSA operation is part of a larger format or protocol.

For an extended overview, see [Rsa Class Overview](https://www.chilkatsoft.com/rsa_class_overview.asp).

## Object creation, unlocking and error handling

**Object Creation**

```sql
DECLARE @hr int
DECLARE @rsa int
EXEC @hr = sp_OACreate 'Chilkat.Rsa', @rsa OUT
IF @hr <> 0
BEGIN
    PRINT 'Failed to create ActiveX component'
    RETURN
END

-- ... use @rsa ...

EXEC @hr = sp_OADestroy @rsa
```

T-SQL uses the Chilkat ActiveX through the OLE Automation stored procedures. They must be enabled once on the server (`EXEC sp_configure 'Ole Automation Procedures', 1; RECONFIGURE;`), and the Chilkat ActiveX registered must match the bitness of the SQL Server instance (64-bit for a 64-bit SQL Server). To bind to a specific major version of Chilkat, append the major version number to the ProgID, such as `sp_OACreate 'Chilkat.Rsa.11'` for Chilkat v11.\*.\*.

`sp_OACreate` returns an object token (an `int`) that is passed as the first argument of every `sp_OAMethod`, `sp_OAGetProperty` and `sp_OASetProperty` call, and released with `sp_OADestroy`. Objects returned by methods (such as an `HttpResponse` or `JsonObject`) are also tokens received through an `int` OUT parameter; they must likewise be destroyed, and the OUT parameter is `NULL` when the method fails to return an object. Objects passed as arguments are passed by their token. When an OLE Automation procedure itself fails (non-zero `@hr`), `sp_OAGetErrorInfo` describes the error.

Data types: strings are `nvarchar(4000)`; integers, booleans (1 or 0) and object tokens are `int`; dates are `datetime`. In the signatures on this page, `@success`, `@iResult`, `@sResult` and the like are the OUT variables receiving a method's return value, `@iValue` / `@sValue` receive or supply a property value, and the remaining `@` variables are the method's arguments in order.

A string returned through an OUT parameter is limited to 4000 characters. For longer values, retrieve the result as a result set into a table variable instead of an OUT parameter, for example `DECLARE @tmp TABLE (outputLine ntext)` followed by `INSERT INTO @tmp EXEC sp_OAGetProperty @rsa, 'LastErrorText'`. See [string length limitations for strings returned by sp_OAMethod calls](https://www.chilkatsoft.com/sql_server_nvarchar_max_limitation.asp).

Methods that pass or return raw byte arrays are not shown on this page, because `varbinary(max)` values cannot be exchanged through `sp_OAMethod` (see [varbinary(max) limitation](https://www.chilkatsoft.com/sql_server_varbinary_max_limitation.asp)). Use the `BinData`-based alternatives (methods ending in *Bd*) or the base64 / hex string-encoded variants instead. Binary *properties* (such as `LastBinaryResult`) can be retrieved as a result set into a table variable, as shown in their signatures. Asynchronous (*\*Async*) methods and event callbacks are not available from SQL Server.

Call `Global.UnlockBundle` once at the start of the program, before using this or any other Chilkat class. Any string unlocks a fully functional 30-day trial; a purchased unlock code is used in production. See `guide.md` for the exact code in SQL Server.

How failure is reported depends on the method's return type and is stated in the note under each method below. In every case the diagnostic text is in the `LastErrorText` property of the object whose method was called.

## Members common to every Chilkat class

Documented once per language in `common-members.md`; listed here so this page is self-contained.

| Property | Signature | Access | Meaning |
|---|---|---|---|
| `DebugLogFilePath` | `EXEC sp_OAGetProperty @rsa, 'DebugLogFilePath', @sValue OUT EXEC sp_OASetProperty @rsa, 'DebugLogFilePath', @sValue` | read/write | If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. |
| `LastBinaryResult` | `INSERT INTO @tmp EXEC sp_OAGetProperty @rsa, 'LastBinaryResult'` | read-only | This property is mainly used in SQL Server stored procedures to retrieve binary data from the last method call that returned binary data. |
| `LastErrorHtml` | `EXEC sp_OAGetProperty @rsa, 'LastErrorHtml', @sValue OUT` | read-only | Provides HTML-formatted information about the last called method or property. |
| `LastErrorText` | `EXEC sp_OAGetProperty @rsa, 'LastErrorText', @sValue OUT` | read-only | Provides plain text information about the last called method or property. |
| `LastErrorXml` | `EXEC sp_OAGetProperty @rsa, 'LastErrorXml', @sValue OUT` | read-only | Provides XML-formatted information about the last called method or property. |
| `LastMethodSuccess` | `EXEC sp_OAGetProperty @rsa, 'LastMethodSuccess', @iValue OUT EXEC sp_OASetProperty @rsa, 'LastMethodSuccess', @iValue` | read/write | Indicates the success or failure of the most recent method call: `1` means success, `0` means failure. |
| `LastStringResult` | `EXEC sp_OAGetProperty @rsa, 'LastStringResult', @sValue OUT` | read-only | In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. |
| `LastStringResultLen` | `EXEC sp_OAGetProperty @rsa, 'LastStringResultLen', @iValue OUT` | read-only | The length, in characters, of the string contained in the LastStringResult property. |
| `VerboseLogging` | `EXEC sp_OAGetProperty @rsa, 'VerboseLogging', @iValue OUT EXEC sp_OASetProperty @rsa, 'VerboseLogging', @iValue` | read/write | If set to `1`, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. |
| `Version` | `EXEC sp_OAGetProperty @rsa, 'Version', @sValue OUT` | read-only | Version of the component/library, such as "10.1.0" |

## Member index

| Member | Kind | Signature |
|---|---|---|
| `Charset` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'Charset', @sValue OUT EXEC sp_OASetProperty @rsa, 'Charset', @sValue` |
| `EncodingMode` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'EncodingMode', @sValue OUT EXEC sp_OASetProperty @rsa, 'EncodingMode', @sValue` |
| `LittleEndian` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'LittleEndian', @iValue OUT EXEC sp_OASetProperty @rsa, 'LittleEndian', @iValue` |
| `NoUnpad` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'NoUnpad', @iValue OUT EXEC sp_OASetProperty @rsa, 'NoUnpad', @iValue` |
| `NumBits` | property, read-only | `EXEC sp_OAGetProperty @rsa, 'NumBits', @iValue OUT` |
| `OaepHash` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'OaepHash', @sValue OUT EXEC sp_OASetProperty @rsa, 'OaepHash', @sValue` |
| `OaepLabel` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'OaepLabel', @sValue OUT EXEC sp_OASetProperty @rsa, 'OaepLabel', @sValue` |
| `OaepMgfHash` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'OaepMgfHash', @sValue OUT EXEC sp_OASetProperty @rsa, 'OaepMgfHash', @sValue` |
| `PkcsPadding` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'PkcsPadding', @iValue OUT EXEC sp_OASetProperty @rsa, 'PkcsPadding', @iValue` |
| `PssSaltLen` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'PssSaltLen', @iValue OUT EXEC sp_OASetProperty @rsa, 'PssSaltLen', @iValue` |
| `UncommonOptions` | property, read/write | `EXEC sp_OAGetProperty @rsa, 'UncommonOptions', @sValue OUT EXEC sp_OASetProperty @rsa, 'UncommonOptions', @sValue` |
| `DecryptBd` | method | `EXEC sp_OAMethod @rsa, 'DecryptBd', @success OUT, @bd, @usePrivateKey` |
| `DecryptStringENC` | method | `EXEC sp_OAMethod @rsa, 'DecryptStringENC', @sResult OUT, @str, @usePrivateKey` |
| `EncryptBd` | method | `EXEC sp_OAMethod @rsa, 'EncryptBd', @success OUT, @bd, @usePrivateKey` |
| `EncryptStringENC` | method | `EXEC sp_OAMethod @rsa, 'EncryptStringENC', @sResult OUT, @str, @bUsePrivateKey` |
| `GenKey` | method | `EXEC sp_OAMethod @rsa, 'GenKey', @success OUT, @numBits, @privKey` |
| `SetX509Cert` | method | `EXEC sp_OAMethod @rsa, 'SetX509Cert', @success OUT, @cert, @usePrivateKey` |
| `SignBd` | method | `EXEC sp_OAMethod @rsa, 'SignBd', @success OUT, @bdData, @hashAlgorithm, @bdSig` |
| `SignHashENC` | method | `EXEC sp_OAMethod @rsa, 'SignHashENC', @sResult OUT, @encodedHash, @hashAlg` |
| `SignRawBd` | method | `EXEC sp_OAMethod @rsa, 'SignRawBd', @success OUT, @bd` |
| `SignStringENC` | method | `EXEC sp_OAMethod @rsa, 'SignStringENC', @sResult OUT, @strToBeHashed, @hashAlgorithm` |
| `SnkToXml` | method | `EXEC sp_OAMethod @rsa, 'SnkToXml', @sResult OUT, @filename` |
| `UsePrivateKey` | method | `EXEC sp_OAMethod @rsa, 'UsePrivateKey', @success OUT, @privKey` |
| `UsePublicKey` | method | `EXEC sp_OAMethod @rsa, 'UsePublicKey', @success OUT, @pubKey` |
| `VerifyBd` | method | `EXEC sp_OAMethod @rsa, 'VerifyBd', @success OUT, @bdData, @hashAlgorithm, @bdSig` |
| `VerifyHashENC` | method | `EXEC sp_OAMethod @rsa, 'VerifyHashENC', @success OUT, @encodedHash, @hashAlg, @encodedSig` |
| `VerifyRawBd` | method | `EXEC sp_OAMethod @rsa, 'VerifyRawBd', @success OUT, @bd` |
| `VerifyStringENC` | method | `EXEC sp_OAMethod @rsa, 'VerifyStringENC', @success OUT, @originalString, @hashAlgorithm, @encodedSig` |

Deprecated members are listed at the end of this file with their replacements; do not use them in new code.

## Properties

### Rsa.Charset

`Chilkat 11.7.0 · sqlserver · Rsa · Charset · property · read/write`

```sql
EXEC sp_OAGetProperty @rsa, 'Charset', @sValue OUT
EXEC sp_OASetProperty @rsa, 'Charset', @sValue
```

**Full documentation for this property (same in every language):** [How Charset Affects RSA](https://www.chilkatsoft.com/ai-docs/v/11.7.0/articles/how_charset_affects_rsa.md) · [ANSI Charset Explained](https://www.chilkatsoft.com/ai-docs/v/11.7.0/articles/ansi_charset_explained.md)

This property specifies the character encoding used to represent text as bytes for encryption, decryption, signing, and signature validation. By default, it uses the computer's `ANSI` charset, such as Windows-1252 for locales like the United States, United Kingdom, Western Europe, Australia, and New Zealand.

Most applications are advised to set this property to `UTF-8`. Chilkat plans to change its default to UTF-8 in a future major version to align with current standards. The current default of ANSI stems from a time when UTF-8 was not widely adopted.

### Rsa.EncodingMode

`Chilkat 11.7.0 · sqlserver · Rsa · EncodingMode · property · read/write`

```sql
EXEC sp_OAGetProperty @rsa, 'EncodingMode', @sValue OUT
EXEC sp_OASetProperty @rsa, 'EncodingMode', @sValue
```

This property defines the encoding for methods ending in `ENC`, such as EncryptStringENC. Valid modes include `base64`, `hex`, `hex_lower`, and more. The encoding mode applies to signatures, encrypted data, and hashes used in or returned by a method.

### Rsa.LittleEndian

`Chilkat 11.7.0 · sqlserver · Rsa · LittleEndian · property · read/write`

```sql
EXEC sp_OAGetProperty @rsa, 'LittleEndian', @iValue OUT
EXEC sp_OASetProperty @rsa, 'LittleEndian', @iValue
```

When creating RSA signatures, this property determines the endianness: set it to `1` for little-endian signatures and `0` for big-endian signatures.

See also:

- [RSA Signatures and Endianness](https://cknotes.com/rsa-signatures-and-endianness/)

### Rsa.NoUnpad

`Chilkat 11.7.0 · sqlserver · Rsa · NoUnpad · property · read/write`

```sql
EXEC sp_OAGetProperty @rsa, 'NoUnpad', @iValue OUT
EXEC sp_OASetProperty @rsa, 'NoUnpad', @iValue
```

If `1`, skips unpadding when decrypting. The default is `0`. This property value is typically left unchanged.

### Rsa.NumBits

`Chilkat 11.7.0 · sqlserver · Rsa · NumBits · property · read-only`

```sql
EXEC sp_OAGetProperty @rsa, 'NumBits', @iValue OUT
```

The bit length, such as 2048, of the imported or generated RSA key.

### Rsa.OaepHash

`Chilkat 11.7.0 · sqlserver · Rsa · OaepHash · property · read/write · since 9.5.0.48`

```sql
EXEC sp_OAGetProperty @rsa, 'OaepHash', @sValue OUT
EXEC sp_OASetProperty @rsa, 'OaepHash', @sValue
```

Selects the hash algorithm for use within OAEP padding for encryption. The valid choices are `sha256`, `sha384`, `sha512`, or `sha1`.

The default is SHA1. You'll likely want to change this to to SHA256. The next major version of Chilkat (11.0.0) will change the default to SHA256.

See also:

- [More Information about RSA OAEP Padding for Encryption](https://cknotes.com/more-information-about-rsa-oaep-padding-for-encryption/)

### Rsa.OaepLabel

`Chilkat 11.7.0 · sqlserver · Rsa · OaepLabel · property · read/write · since 9.5.0.95`

```sql
EXEC sp_OAGetProperty @rsa, 'OaepLabel', @sValue OUT
EXEC sp_OASetProperty @rsa, 'OaepLabel', @sValue
```

The optional RSA encryption OAEP label is a hex representation of the label bytes used for encrypting with OAEP padding. Typically, this is left empty (0 bytes) unless there's a specific requirement to set it.

See also:

- [More Information about RSA OAEP Padding for Encryption](https://cknotes.com/more-information-about-rsa-oaep-padding-for-encryption/)

### Rsa.OaepMgfHash

`Chilkat 11.7.0 · sqlserver · Rsa · OaepMgfHash · property · read/write · since 9.5.0.71`

```sql
EXEC sp_OAGetProperty @rsa, 'OaepMgfHash', @sValue OUT
EXEC sp_OASetProperty @rsa, 'OaepMgfHash', @sValue
```

Selects the MGF (mask generation) hash algorithm for use within OAEP padding for encryption. The valid choices are `sha256`, `sha384`, `sha512`, or `sha1`.

Note: This property should typically be set to the same value as the OaepHash property. Many software implementations are not able to handle cases where the MGF hash is different than the OAEP hash.

The default is SHA1. You'll likely want to change this to to SHA256. The next major version of Chilkat (11.0.0) will change the default to SHA256.

See also:

- [More Information about RSA OAEP Padding for Encryption](https://cknotes.com/more-information-about-rsa-oaep-padding-for-encryption/)

### Rsa.PkcsPadding

`Chilkat 11.7.0 · sqlserver · Rsa · PkcsPadding · property · read/write · since 11.0.0`

```sql
EXEC sp_OAGetProperty @rsa, 'PkcsPadding', @iValue OUT
EXEC sp_OASetProperty @rsa, 'PkcsPadding', @iValue
```

This property controls padding for both signing and encryption. The default value is true, which is to use PKCS#1 v1.5 padding. If set to false, then PSS padding is used for signatures and OAEP padding is used for encryption.

This property replaces the deprecated `OaepPadding` property. Until the OaepPadding property is removed, setting this property will automatically set OaepPadding to the opposite, and vice-versa. This is to maintain backward compatibility until applications can switch to using this new property.

### Rsa.PssSaltLen

`Chilkat 11.7.0 · sqlserver · Rsa · PssSaltLen · property · read/write · since 9.5.0.80`

```sql
EXEC sp_OAGetProperty @rsa, 'PssSaltLen', @iValue OUT
EXEC sp_OASetProperty @rsa, 'PssSaltLen', @iValue
```

When using RSASSA-PSS padding for signatures, you can choose the PSS salt length. By default, the salt length is set to -1, which uses the length of the hash function. For instance, with the SHA256 hash function, the salt length will be 32 bytes. You can specify a different salt length, like 20 bytes, if needed, but it's generally recommended to keep the default setting.

### Rsa.UncommonOptions

`Chilkat 11.7.0 · sqlserver · Rsa · UncommonOptions · property · read/write · since 10.1.0`

```sql
EXEC sp_OAGetProperty @rsa, 'UncommonOptions', @sValue OUT
EXEC sp_OASetProperty @rsa, 'UncommonOptions', @sValue
```

This is a catch-all property to be used for uncommon needs. This property defaults to the empty string and should typically remain empty.

## Methods

### Rsa.DecryptBd

`Chilkat 11.7.0 · sqlserver · Rsa · DecryptBd · method · since 9.5.0.76`

```sql
EXEC sp_OAMethod @rsa, 'DecryptBd', @success OUT, @bd, @usePrivateKey
```

RSA decrypts the contents of `bd`. `usePrivateKey` should be set to `1` if the private key is to be used for decrypting. Otherwise it should be set to `0` if (in rare cases) the public key is to be used for decrypting.

**Important:** If trying to match OpenSSL results, set the LittleEndian property = `0`.

Returns 1 for success, 0 for failure.

See also:

- [RSA Encryption Maximum Number of Bytes](https://cknotes.com/rsa-encryption-maximum-number-of-bytes/)

### Rsa.DecryptStringENC

`Chilkat 11.7.0 · sqlserver · Rsa · DecryptStringENC · method`

```sql
EXEC sp_OAMethod @rsa, 'DecryptStringENC', @sResult OUT, @str, @usePrivateKey
```

Decrypts `str` with the RSA algorithm. `str` is the encoded form of the encrypted binary data. The EncodingMode property defines `str`'s encoding. The Charset property specifies the byte representation for interpreting the decrypted text. Set `usePrivateKey` to `1` to use the private key for decryption; otherwise, set `usePrivateKey` to `0` to use the public key (used rarely). Returns the decrypted string.

**Important:** If trying to match OpenSSL results, set the LittleEndian property = `0`.

Returns `NULL` on failure

### Rsa.EncryptBd

`Chilkat 11.7.0 · sqlserver · Rsa · EncryptBd · method · since 9.5.0.76`

```sql
EXEC sp_OAMethod @rsa, 'EncryptBd', @success OUT, @bd, @usePrivateKey
```

RSA encrypts the contents of `bd`. Set `usePrivateKey` to `0` to use the public key for encrypting; otherwise, set it to `1` to use the private key (in rare cases).

**Important:** If trying to match OpenSSL results, set the LittleEndian property = `0`.

**Note:** The public key's role is to make encryption accessible to anyone while ensuring that only the private key holder can decrypt the messages. The public key is designed to be widely distributed so anyone can use it to encrypt messages intended for the owner of the private key.

Returns 1 for success, 0 for failure.

See also:

- [RSA Encryption Maximum Number of Bytes](https://cknotes.com/rsa-encryption-maximum-number-of-bytes/)

### Rsa.EncryptStringENC

`Chilkat 11.7.0 · sqlserver · Rsa · EncryptStringENC · method`

```sql
EXEC sp_OAMethod @rsa, 'EncryptStringENC', @sResult OUT, @str, @bUsePrivateKey
```

Encrypts `str` with the RSA algorithm. The Charset property specifies the byte representation of the string that is encrypted. Set `bUsePrivateKey` to `0` to use the public key for encrypting; otherwise, set it to `1` to use the private key (in rare cases). The encrypted data is returned in the format specified by the EncodingMode property.

**Important:** If trying to match OpenSSL results, set the LittleEndian property = `0`.

**Note:** The public key's role is to make encryption accessible to anyone while ensuring that only the private key holder can decrypt the messages. The public key is designed to be widely distributed so anyone can use it to encrypt messages intended for the owner of the private key.

Returns `NULL` on failure

### Rsa.GenKey

`Chilkat 11.7.0 · sqlserver · Rsa · GenKey · method · since 11.0.0`

```sql
EXEC sp_OAMethod @rsa, 'GenKey', @success OUT, @numBits, @privKey
```

Generates a new RSA key and stores it in `privKey`. `numBits` specifies the key length, which can range from 512 to 8192 bits. Common key lengths are 1024, 2048, or 4096 bits.

Note: Generating an 8192-bit key may take a significant amount of time. The method does not support event callbacks or progress monitoring and will block the thread until completion.

Returns 1 for success, 0 for failure.

### Rsa.SetX509Cert

`Chilkat 11.7.0 · sqlserver · Rsa · SetX509Cert · method · since 9.5.0.73`

```sql
EXEC sp_OAMethod @rsa, 'SetX509Cert', @success OUT, @cert, @usePrivateKey
```

Provides the private or public key indirectly through a certificate. This method is used when the private key is inaccessible, such as when stored on a smart card, USB token, in the Windows registry (marked as non-exportable), or in the Apple Keychain.

Returns 1 for success, 0 for failure.

### Rsa.SignBd

`Chilkat 11.7.0 · sqlserver · Rsa · SignBd · method · since 9.5.0.77`

```sql
EXEC sp_OAMethod @rsa, 'SignBd', @success OUT, @bdData, @hashAlgorithm, @bdSig
```

Generates an RSA digital signature by first hashing the contents of `bdData` with the hash algorithm specified by `hashAlgorithm`, which can be `sha256`, `sha384`, `sha512`, or `sha1`. The resulting signature is written to `bdSig`.

Note: It is important to be aware of endianness. Make sure the LittleEndian property is set according to your specific needs.

Returns 1 for success, 0 for failure.

### Rsa.SignHashENC

`Chilkat 11.7.0 · sqlserver · Rsa · SignHashENC · method`

```sql
EXEC sp_OAMethod @rsa, 'SignHashENC', @sResult OUT, @encodedHash, @hashAlg
```

This function creates an RSA digital signature for the hash provided in `encodedHash`, which should be encoded according to the EncodingMode setting (e.g., base64 if EncodingMode = `base64`). `hashAlg` specifies the hash algorithm and can be `sha256`, `sha384`, `sha512`, or `sha1`. The function returns the signature encoded as specified by EncodingMode.

Returns `NULL` on failure

### Rsa.SignRawBd

`Chilkat 11.7.0 · sqlserver · Rsa · SignRawBd · method · since 11.0.0`

```sql
EXEC sp_OAMethod @rsa, 'SignRawBd', @success OUT, @bd
```

This is legacy low-level raw RSA that duplicates the (now deprecated) `OpenSSL` `rsautl` utility. It directly signs raw data rather than signing a hash of the data. PKCS#1 v1.5 padding is always used. The data to be signed is passed in `bd`, and on return the content of `bd` is replaced with the RSA signed data.

Note: It is possible to validate and recover the original data by calling `VerifyRawBd`.

Returns 1 for success, 0 for failure.

### Rsa.SignStringENC

`Chilkat 11.7.0 · sqlserver · Rsa · SignStringENC · method`

```sql
EXEC sp_OAMethod @rsa, 'SignStringENC', @sResult OUT, @strToBeHashed, @hashAlgorithm
```

Generates an RSA digital signature by first hashing `strToBeHashed` with the hash algorithm specified by `hashAlgorithm`, which can be `sha256`, `sha384`, `sha512`, or `sha1`. Returns the signature encoded based on the EncodingMode property.

**Note:** It is important to be aware of endianness. Make sure the LittleEndian property is set according to your specific needs.

**Note:** It is recommended to set the Charset property equal to `utf-8` before signing strings.

Returns `NULL` on failure

### Rsa.SnkToXml

`Chilkat 11.7.0 · sqlserver · Rsa · SnkToXml · method`

```sql
EXEC sp_OAMethod @rsa, 'SnkToXml', @sResult OUT, @filename
```

Imports a .snk file to an XML document that can be imported via the ImportPrivateKey method.

Returns `NULL` on failure

### Rsa.UsePrivateKey

`Chilkat 11.7.0 · sqlserver · Rsa · UsePrivateKey · method · since 11.0.0`

```sql
EXEC sp_OAMethod @rsa, 'UsePrivateKey', @success OUT, @privKey
```

Imports a private key from `privKey` to use for signing or decrypting.

Returns 1 for success, 0 for failure.

### Rsa.UsePublicKey

`Chilkat 11.7.0 · sqlserver · Rsa · UsePublicKey · method · since 11.0.0`

```sql
EXEC sp_OAMethod @rsa, 'UsePublicKey', @success OUT, @pubKey
```

Imports a public key from `pubKey` to use for encrypting or signature verification.

Returns 1 for success, 0 for failure.

### Rsa.VerifyBd

`Chilkat 11.7.0 · sqlserver · Rsa · VerifyBd · method · since 9.5.0.77`

```sql
EXEC sp_OAMethod @rsa, 'VerifyBd', @success OUT, @bdData, @hashAlgorithm, @bdSig
```

Verifies the RSA signature passed in `bdSig` against the original data passed in `bdData`. The original data passed in `bdData` is hashed using the hash algorithm passed in `hashAlgorithm` (such as `sha256`, `sha384`, `sha512`, or `sha1`). Returns `1` if the signature is validated, and `0` if not.

Note: Knowing the exact hash algorithm used to create the signature is not required. If the signature is not validated using the hash algorithm specified in `hashAlgorithm`, Chilkat will automatically try validating using the other supported algorithms and return success if any validate.

Returns 1 for success, 0 for failure.

### Rsa.VerifyHashENC

`Chilkat 11.7.0 · sqlserver · Rsa · VerifyHashENC · method`

```sql
EXEC sp_OAMethod @rsa, 'VerifyHashENC', @success OUT, @encodedHash, @hashAlg, @encodedSig
```

Validates an RSA signature provided in `encodedSig` against the hash of the original data in `encodedHash`. Returns `1` if validation is successful, otherwise returns `0`. `hashAlg` specifies the hash algorithm used for `encodedHash`, such as `sha256`, `sha384`, `sha512`, or `sha1`. Ensure the hash's size (e.g., 32 bytes for sha256, 48 bytes for sha384, 64 bytes for sha512, 20 bytes for sha1) matches that of `encodedHash`.

Both `encodedHash` and `encodedSig` should be encoded according to the EncodingMode property (e.g., base64 if EncodingMode = `base64`)

Returns 1 for success, 0 for failure.

### Rsa.VerifyRawBd

`Chilkat 11.7.0 · sqlserver · Rsa · VerifyRawBd · method · since 11.0.0`

```sql
EXEC sp_OAMethod @rsa, 'VerifyRawBd', @success OUT, @bd
```

This is legacy low-level raw RSA that duplicates the (now deprecated) `OpenSSL` `rsautl` utility. It validates signed raw data and recovers the original data. The RSA signature to be verified is passed in `bd`, and on return the content of `bd` is replaced with the original data.

Returns 1 for success, 0 for failure.

### Rsa.VerifyStringENC

`Chilkat 11.7.0 · sqlserver · Rsa · VerifyStringENC · method`

```sql
EXEC sp_OAMethod @rsa, 'VerifyStringENC', @success OUT, @originalString, @hashAlgorithm, @encodedSig
```

Verifies the encoded RSA signature passed in `encodedSig` against the original data passed in `originalString`. The original data passed in `originalString` is hashed using the hash algorithm passed in `hashAlgorithm` (such as `sha256`, `sha384`, `sha512`, or `sha1`). Returns `1` if the signature is validated, and `0` if not.

The signature passed in `encodedSig` should be encoded according to the EncodingMode property (e.g., base64 if EncodingMode = `base64`)

Note: Knowing the exact hash algorithm used to create the signature is not required. If the signature is not validated using the hash algorithm specified in `hashAlgorithm`, Chilkat will automatically try validating using the other supported algorithms and return success if any validate.

Returns 1 for success, 0 for failure.

## Deprecated members — do not use in new code

| Member | Kind | Deprecated in | Use instead |
|---|---|---|---|
| `OaepPadding` | property | before 11.6.1 | — |
| `ExportPrivateKey` | method | before 11.6.1 | — |
| `ExportPrivateKeyObj` | method | before 11.6.1 | — |
| `ExportPublicKey` | method | before 11.6.1 | — |
| `ExportPublicKeyObj` | method | before 11.6.1 | — |
| `GenerateKey` | method | before 11.6.1 | `GenKey` |
| `ImportPrivateKey` | method | before 11.6.1 | `UsePrivateKey` |
| `ImportPrivateKeyObj` | method | before 11.6.1 | `UsePrivateKey` |
| `ImportPublicKey` | method | before 11.6.1 | `UsePublicKey` |
| `ImportPublicKeyObj` | method | before 11.6.1 | `UsePublicKey` |
| `OpenSslSignBd` | method | before 11.6.1 | `SignRawBd` |
| `OpenSslSignStringENC` | method | before 11.6.1 | `SignRawBd` |
| `OpenSslVerifyBd` | method | before 11.6.1 | `VerifyRawBd` |
| `OpenSslVerifyStringENC` | method | before 11.6.1 | `VerifyRawBd` |

## Related classes

[`BinData`](https://www.chilkatsoft.com/ai-docs/v/11.7.0/sqlserver/classes/BinData.md), [`Cert`](https://www.chilkatsoft.com/ai-docs/v/11.7.0/sqlserver/classes/Cert.md), [`PrivateKey`](https://www.chilkatsoft.com/ai-docs/v/11.7.0/sqlserver/classes/PrivateKey.md), [`PublicKey`](https://www.chilkatsoft.com/ai-docs/v/11.7.0/sqlserver/classes/PublicKey.md)

