Visual FoxPro

Windows Credentials Manager - AutoSplit Larger Secrets

See more Secrets Examples

Secrets stored in the Windows Credentials Manager can be a maximum of 2560 bytes in size. If the content of the secret is too large for the Windows Credential Manager, Chilkat will automatically split the secret into parts and store a shorter JSON manifest.

Note: This example requires Chilkat v10.1.0 or later.

Visual FoxPro

LOCAL lnSuccess
LOCAL loSecrets
LOCAL loJson
LOCAL loJsonSecret

lnSuccess = 0

* This example requires the Chilkat API to have been previously unlocked.
* See Global Unlock Sample for sample code.

loSecrets = CreateObject('Chilkat.Secrets')

* The default value of AutoSplit is 1.
* Note: AutoSplit only applies when the secret location is "local_manager"
* and the app is running on the Windows OS.  All other secret locations, such as Apple Keychain,
* AWS Secrets Manager, Azure Key Vault, etc. don't have limitations that are so small.
loSecrets.AutoSplit = 1

* On Windows, this is the Windows Credentials Manager
* On MacOS/iOS, it is the Apple Keychain
* (This example is explaining how a secret too large for the Windows Credential Manager
* is automatically compressed and split into parts if needed.)
loSecrets.Location = "local_manager"

* Specify the name of the secret.
* service and username are required.
* appName and domain are optional.
* Note: The values are arbitrary and can be anything you want.
loJson = CreateObject('Chilkat.JsonObject')
loJson.UpdateString("appName","AA_MyApp")
loJson.UpdateString("service","OAuth2")
loJson.UpdateString("domain","onedrive")
loJson.UpdateString("username","matt")

* Get the secret to be stored.
loJsonSecret = CreateObject('Chilkat.JsonObject')
lnSuccess = loJsonSecret.LoadFile("qa_data/tokens/oneDrive.json")
IF (lnSuccess = 0) THEN
    ? loJsonSecret.LastErrorText
    RELEASE loSecrets
    RELEASE loJson
    RELEASE loJsonSecret
    CANCEL
ENDIF

* Note: The oneDrive.json file we used for testing is 4824 bytes in size,
* which exceeds the maximum size (2560 bytes) allowed by the Windows Credentials Manager.

* When the size is too large, Chilkat will first compress the content of the secret.
* If the compressed size is small enough, then it is stored compressed without splitting.
* Otherwise the compressed data is split

* Your application does not need to know how the secret is stored in the Windows Credentials Manager.
* When fetching the secret, Chilkat automatically decompresses and re-composes from parts.

* Create or update the secret.
lnSuccess = loSecrets.UpdateSecretJson(loJson,loJsonSecret)
IF (lnSuccess = 0) THEN
    ? loSecrets.LastErrorText
    RELEASE loSecrets
    RELEASE loJson
    RELEASE loJsonSecret
    CANCEL
ENDIF

* This is the auto-split secret viewed in the Windows Credentials Manager:
* 

* Note: If you delete the auto-split secret by calling Chilkat's DeleteSecret method,
* the parts are automatically deleted.
* Also, if you update the secret, the old parts are automatically deleted and new parts are created.

? "Success"

RELEASE loSecrets
RELEASE loJson
RELEASE loJsonSecret