Reference · OpenPGP

Integrate against a signed file

Detached, clear-signed or inline; armored or binary. The keys below are the shared demo pair, one standing in for your app and one for the counterparty, so the whole exchange is followable without an account.

What are you working with

What are you testing?

What crosses the wire

Not sure which of these you need?

No OpenPGP keysets yet

A keyset holds the keys for one file feed, and everything below needs one. Creating it takes a few seconds and asks nothing you have to look up.Create an OpenPGP keyset

Reference

URL or embedded key?

Your app needs the public key to check a token. It can fetch it from a URL at runtime, or carry it as a file. Both are normal. The trade is always the same one: who controls rotation.

	Fetch from the URL	Embed the key
Rotation	Automatic on next fetch	Needs a redeploy
Network	Depends on the URL	None
Trust	Whatever the endpoint serves	Pinned to one key
Suits	A signer that rotates keys	Offline, air-gapped, or pinned

Use the URL when the signer rotates its keys, which is what every identity provider does. That is why it became the norm, and it is usually a one-line config change.

Embed the key when you cannot make a network call while checking a token, or when you want your app pinned to one key so a compromised endpoint could not introduce another. Export the PEM from the Keysets tab.

One catch worth knowing: Spring Boot's public-key-location only loads RSA keys. An ES256 or EdDSA key needs a custom decoder, or the URL.