LogoLogo
HomeIntegrityControlSolutionsManagement Center
3.1.0 Enrollment
3.1.0 Enrollment
  • THE SERVICE
    • Overview
    • About this release
      • Release notes
      • Breaking changes
    • Get started
    • Installation
      • Container
      • Linux
      • Windows
  • Modules
    • Overview
    • AuthN
    • Enrollment
      • Overview
      • Properties
      • OATH Software Token
        • Overview
        • Properties
      • OATH Hardware Token
        • Overview
        • Properties
      • Passkey
        • Overview
        • Properties
      • Fortified ID mobile
        • Overview
        • Properties
    • TokenAdminApi
      • Overview
      • Properties
      • HTTP API
    • TokensDb
      • Overview
      • Properties
      • OATH Software (oathsw)
      • OATH Hardware (oathhw)
      • Passkey (webauthn)
        • Public Key Credential Creation Options (credential_creation_options)
    • Other modules
  • Operations
    • Database
      • Connect to database
      • Operate
      • Troubleshoot
    • Troubleshooting
      • Extended logging
    • CEF logging
    • PSKC File Import
  • Token devices
    • OATH mobile apps
  • Installation
    • Using a container
    • Windows
    • Unix
Powered by GitBook
On this page
  1. Operations

PSKC File Import

Importing hardware tokens from PSKC file

PreviousCEF loggingNextOATH mobile apps

To import hardware token data into the database, use the API that is exposed by the (TokenAdminApi) module. This API consumes files and supports TOTP and HOTP tokens.

Security

PSKC files contains sensitive data and should be protected.

PRIVATE KEYS

Encryption is a part of the PSKC standard. Location of secret keys need to be added via the server configuration before encrypted PSKC files can be handled. Location of private keys is a configuration parameter in the TokensDb module and the secret_key_directory parameter, see module for more information. Make sure that no unauthorised access is possible to the directory where the secret keys reside.

IN FLIGHT

Protect the file while being uploaded to the Token Admin API by enabling TLS.

AT REST

The uploaded file ends up in the upload directory on the server. Make sure that no unauthorized access is possible to this directory.

After the import is completed (or failed), the system deletes the imported file, and emits a to indicate that the file was successfully deleted. Failure of this log message to appear means that the file might remain in the upload directory and indicates a possible security threat. In that case, the file should be manually deleted.

Token Administration
PSKC XML
CEF log entry