Managing keys

The Keys page is where you manage every key your protected files use. There are three kinds, each with one job. Knowing which is which makes the rest of Oxrion fall into place.

License keys

A license key pairs a protected file with its license. You choose one when you mark a file as Licensed in the Encoder, then use the same key in the Licenser to issue a .lic for a customer’s domain and expiry.

• Generated for you as a secure random value, or enter your own.
• Give each one a name (e.g. the customer or product) to tell them apart.

Deleting a license key doesn’t break files already encrypted with it — but you won’t be able to issue new licenses for that key.

External keys

An external key is what makes Private access work. A private file requires its matching external key to be present on the server at runtime; without it, the file won’t run even with the Loader installed.

• Generated for you, or enter your own.
• Named, so you can manage several across different deployments.

Setting one up on a server is covered in External keys on a server.

Recovery keypairs

A recovery keypair lets you restore a protected file back to source. It’s a true public/private key pair, and how it’s handled is central to Oxrion’s design.

When you create a keypair, Oxrion stores only the public key. The private key is shown once, downloaded immediately, and never kept by Oxrion.

Caution

Save your private key the moment it appears — it’s shown only once and never stored on our side. If you lose it, files encrypted with its public key can never be recovered, by anyone.

You can also bring your own: paste a public key you already hold and keep its private key entirely on your side. Either way, only the public key lives in Oxrion.

Three keys, three jobs

Key	What it does	Stored by Oxrion?
License key	Pairs a file with a customer’s license	Yes
External key	Required on the server to run a private file	Yes
Recovery keypair	Restores a protected file to source	Public key only — never the private key