SafeKey
  • Introduction To SafeKey
  • Getting Started
    • Choosing Your SafeKey(s)
      • Which SafeKey do I need?
      • How many SafeKeys do I need?
      • SafeKey Comparison
      • Orders & Shipment
    • First Time Using Your SafeKey
      • Best Practices
      • SafeKey as Security Key
      • SafeKey as Secure Storage Device for Encrypted Data
    • Glossary
  • Use Cases
    • Two-Factor Authentication
    • Passwordless Logins
    • Phishing Protection
    • Decentralized and Encrypted Backups
    • Digital Inheritance
  • Tools
    • SafeKey Desktop Tool
    • Inheriti®
    • SafeKey Mobile
      • Changelog
  • User Guides
    • SafeKey Settings
    • Firmware Update
    • SafeKey Authenticity Check
    • PIN Code Management
    • Registration Test
    • Login Test
    • Factory Reset
    • Backups
      • Create Backups
      • Restore Backups
      • Identical SafeKey Devices
  • Technicals
    • Metadata
    • Certificates
    • Hardware
    • Identification
    • Patents
    • Licensing
  • Developers
    • Introduction
    • PHP Software Libraries (FIDO2)
    • Javascript Libraries (CS)
    • Python CLI Tools (CS)
    • SafeKey Protocol (CS)
    • High-Level Design Docs (CS)
Powered by GitBook
On this page

Was this helpful?

  1. Developers

Introduction

Developers section of the SafeKey documentation.

In this section you can find different tools, libraries and explanations about how you can integrate SafeKey into your own projects.

Our CLI tools and JavaScript libraries make it easy for web developers to integrate and provide SafeKey support in their websites and webapplications.

The Custom Storage (CS) feature allows for the safe storage of at least 350 bytes of data per record and the ability to backup data. The device's interface is available over-browser and supports multiple domains.

The Custom Storage is encrypted with AES256 and can only be accessed after providing the correct PIN, which is shared with the FIDO2 PIN application for ease of use.

Data is stored as received from the JavaScript application, encoded in CBOR structure, and the FIDO U2F is used as the transport layer for backward compatibility and internet browser communication.

The primary use case for SafeKey is to provide storage for the private keys, shares of data strings or other secrets that can be used to access accounts, assets or data in larger databases.

In addition we have created multiple libraries to enable web developers to integrate FIDO compatibility into their websites and start providing FIDO support with ease.

We hope these developer docs will help you to integrate SafeKey in your own projects.

Last updated 8 months ago

Was this helpful?