Keyfactor Signature Provider
SPSDK Signature Provider plugin using Keyfactor's API
Features
- Allows SPSDK to use Keyfactor for signing any arbitrary data
- Users might be authenticated using Client Certificates
Installation
- Activate virtual env, where you have SPSDK
- to install spsdk run:
pip install spsdk
- to install spsdk run:
pip install spsdk_keyfactor
Usage
All of plugin configuration can be done via environment variables:
KEYFACTOR_HOST: URL of the Keyfactor host (example: "https://ray-signserver.keyfactoriot.com")KEYFACTOR_HOST_VERIFY: Path to a TLS certificate to verify the HOST (example: "ejbcav8demo.keyfactoriot.com.pem")KEYFACTOR_AUTH_TYPE: Type of authentication in Keyfactorclient_certificate_keyusing client x509 certificate and private keyclient_certificate_pkcs12using client PKCS#12 certificate and password (password might be stored in a file, and then password is a path to a file with the password to PKCS#12 certificate)
KEYFACTOR_AUTH_VALUE: Coma-separated string of values described byKEYFACTOR_AUTH_TYPE(example for PKCS#12: "path_to_pkcs.p12,path_to_pass.txt")KEYFACTOR_WORKER: Name or ID of the Keyfactor Worker to use (example: "PlainSigner")KEYFACTOR_PREHASH: Client-side pre-hashing of data (example: "SHA-256", "SHA-384")KEYFACTOR_SIGNATURE_LENGTH: Length in bytes of the raw signature (without potential DER encoding) (example: 256 for RSA, 64 for ECC-256)- if this setting is skipped, the plugin will autodetect the value
Environment variables may be specified in a file.
By default the plugin searches for file named .keyfactor.env in the following locations: CWD, HOME, ~/.config
The path to env file also be set via environment variable KEYFACTOR_DOTENV_PATH
Plugin comes with an companion app (nxp-keyfactor) which you may use to create a configuration file template.
To generate a configuration file, run: nxp-keyfactor get-template
Once the plugin is configured, you may use it everywhere in SPSDK config files where a path to a private key or signature provider is mentioned. The identifier for this plugin is keyfactor.
Example: signProvider: type=keyfactor[;worker=myWorker]
- (setting the worker name/id in SPSDK config file overrides the KEYFACTOR_WORKER setting)
When you need to download a public key corresponding to your Keyfactor worker (e.g.: SRK_TABLE for AHAB) you can use the companion app.
Example: nxp-keyfactor get-puk --worker PlainSigner --output my_public_key.pem
Credits
This package was created with Cookiecutter and the SPSDK Signature Provider project template.
Metadata
Release files for spsdk-keyfactor 0.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| spsdk_keyfactor-0.4.5.tar.gz | 10.9 kB | Details |
Release files / spsdk_keyfactor-0.4.5.tar.gz
| Download URL | spsdk_keyfactor-0.4.5.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f678237f9d7229cff433f5e27ad01ae7ff81e84af310d872fdbefed068e1a16
|
|
BLAKE2b-256 checksum How to use checksums |
69f0205b005b6b3040760995ed8169a1705495a67750edec761050f356d56f6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency log