--- title: "Key Management Tool prerequisites" slug: "a3s-kmg-nshield-key-management-tool-prerequisites-4-0" updated: 2026-11-11T09:30:14Z published: 2026-11-11T09:30:14Z canonical: "docs.onespan.com/a3s-kmg-nshield-key-management-tool-prerequisites-4-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Key Management Tool prerequisites ## Hardserver configuration Key Management Tool provided with Authentication Suite Server SDK for Entrust nShield HSM uses the hardserver that is installed with the Entrust nShield software package. Before launching the manager on the client machine, install and configure the Entrust nShield support software. For more information, refer to the Entrust nShield documents related to the installation and configuration for the Entrust nShield. ## User data file generation In addition, the keys created by Key Management Tool are protected by the module (Security World Key) but also by the customer’s SEE code signing key with which the customer will have signed its user data file (userdata.sar). It is **mandatory** to first generate the signed user data file (userdata.sar), and to then have this signed user data file available on the client machine in the nfast key management data directory (usually kmdata for [nShield XC](/secsdks/docs/a3s-mmg-nshield-xc-prepare-authentication-suite-server-sdk-see-machine-4-0) or kmdata/local for [nShield 5](/secsdks/docs/a3s-mmg-nshield-5-prepare-authentication-suite-server-sdk-see-machine-4-0)) before launching the manager tool.