How it works

How your two signing keys work

Your ClientDB uses two Ed25519 keys. One shows the ID-Truster Hub that calls come from you. The other lets the app check every answer against your own DNS.

Your ClientDB uses two Ed25519 keys. The connection key signs every call your ClientDB makes to the ID-Truster Hub. The answer key signs every answer and message your ClientDB sends to the app. This article covers where your keys are, who checks them, and what the app checks before it shows your business card. How the parts connect is in How the ID-Truster ecosystem fits together.

Where your keys are

Key Signs Checked by Public key stored
Connection key Calls from your ClientDB to the Hub The Hub In the Hub. You send it when you set up ClientDB
Answer key Answers and messages from your ClientDB to the app The app In your DNS at _idtruster.<your domain>, protected with DNSSEC

Both private keys are stored only in your ClientDB. They never leave your systems and are never sent to ID-Truster.

Who checks what

  • The Hub checks the connection key. Every call from your ClientDB to the Hub carries your username, password and token, and is signed with your connection key. The Hub checks the signature with the public key you sent when you set up ClientDB. A stolen password and token are not enough to call the Hub as your company.
  • The app checks the answer key. Every answer and message from your ClientDB is signed with your answer key. The app fetches the public key from your DNS and checks the signature before it shows your customer anything.

Because the public part of your answer key is in your DNS and not at ID-Truster, the Hub cannot fake an answer from you, and no other company in the ecosystem can either.

What the app checks before it shows your business card

Before the app shows your business card to your customer, it checks the answer from your ClientDB. The answer is signed with your answer key, and the app checks the signature against the public key you have placed in DNS on your own domain. If the signature does not check out, the app shows “This message could not be verified. Treat it as not genuine.”

The ID-Truster app showing the business card for Demo Bank with the badge Verified by ID-Truster
The signature checks out. Your customer sees your business card.
The ID-Truster app showing Could not verify code. This message could not be verified. Treat it as not genuine.
The signature does not check out. Your customer is told not to trust the message.

The check step by step is in How a trust code is verified.

Questions about your signing keys

  • Why are there two keys?

    They check two different things. The connection key lets the ID-Truster Hub check that a call comes from your ClientDB, and not just from someone with your username, password and token. The answer key lets the app check that an answer comes from you, without trusting anything stored at ID-Truster.

  • Can ID-Truster fake an answer from our ClientDB?

    No. The answer is signed with your answer key, and the app checks the signature against the public key in your own DNS, not against anything stored at ID-Truster. A breach at ID-Truster alone cannot fake your answer.

  • Where are our private keys stored?

    Only in your ClientDB. Neither private key leaves your systems or is sent to ID-Truster. When you set up ClientDB, you send the ID-Truster Hub only the public part of your connection key.

  • Is DNSSEC required?

    Yes. The public part of your answer key is in your own DNS, and the record must be protected with DNSSEC.

See the answer key at work. Follow a trust code from the moment your customer taps Check until the answer is on screen.

How a trust code is verified

How it works

More on how it works