NKeys
NKeys are a new, highly secure public-key signature system based on Ed25519.
With NKeys the server can verify identities without ever storing or ever seeing private keys. The authentication system works by requiring a connecting client to provide its public key and digitally sign a challenge with its private key. The server generates a random challenge with every connection request, making it immune to playback attacks. The generated signature is validated against the provided public key, thus proving the identity of the client. If the public key is known to the server, authentication succeeds.
NKey is an excellent replacement for token authentication because a connecting client will have to prove it controls the private key for the authorized public key.
To generate nkeys, you'll need the nk
tool.
Generating NKeys and Configuring the Server
To generate a User NKEY:
The first output line starts with the letter S
for Seed. The second letter, U
stands for User. Seeds are private keys; you should treat them as secrets and guard them with care.
The second line starts with the letter U
for User and is a public key which can be safely shared.
To use nkey authentication, add a user, and set the nkey
property to the public key of the user you want to authenticate:
Note that the user section sets the nkey
property (user/password/token properties are not needed). Add permission
sections as required.
Client Configuration
Now that you have a user nkey, let's configure a client to use it for authentication. As an example, here are the connect options for the node client:
The client provides a function that it uses to parse the seed (the private key) and sign the connection challenge.
Last updated