Skip to main content
Skip table of contents

Managing Remote Authenticators

The following provides information about how to manage Remote Authenticators.

For more information about the concepts of Remote Authenticators, see Remote Authenticators Overview.


The following actions are available from the Remote Authenticators page (System Functions → Remote Authentication):




Marks the Internal Key Binding as Active/Disabled. Only Active ones will be used and processed by health-check.


Removes the Internal Key Binding, but will not remove the referenced key pair or certificates.

New keys

Generates a new key pair in the referenced Crypto Token using the same key specification as the current key has and an alias derived from the current alias.


Creates a Certificate Signing Request using the next key pair (or current key pair when no next key pair exists).


Searches the database for the latest issued matching certificate for the next key pair (or current key pair when no next key pair exists) by using SubjectKeyId.


When the CA that issued the current certificate is active and resides in the same instance, this will create a new certificate using the same End Entity as the last one was issued with. If a next key pair exists, that key pair will be used.


Setting up a Remote Authenticator

Remote Authenticators are used to establish mutual TLS, from the upstream node to the downstream node. Thus the Remote Authenticator needs to be established on the upstream node (commonly the CA) and the signing CA (commonly the Management CA) needs to be recognized on the downstream node (commonly a VA or RA).

Setting up a Remote Authenticator

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.