Skip to main content
Credentials normally sit centrally in the Vault of Docusnap365: encrypted in the browser, usable at every gateway of our subscription afterwards. For credentials that are not to leave your own network there is a second route: credentials stored on the gateway itself. We create such an entry, find it again in the browser and see what sets it apart from the central route.
The prerequisite is an installed and registered gateway, see Installing and Registering the Gateway.

​
Creating the entry on the gateway

1

Open the credentials

In the gateway window on the gateway host we open the Credentials tab. It can only be operated after the registration.
2

Set type and identifier

Add opens the New Credentials dialog. Six of the seven types are available—Entra ID App only when editing an existing entry. As the Identifier we allow only a-z A-Z 0-9 äöüÄÖÜß _ -. Without an identifier, Apply stays disabled, and the dialog rejects an identifier that is already in use.
Type and identifier can no longer be changed after creation—the identifier is at the same time the file name of the encrypted file. To rename an entry or give it a different type, we create a new one and delete the old one.
3

Fill in the fields and apply

Depending on the chosen type the matching fields appear—for User Account for instance Username and Password. Apply encrypts the entry and saves it.
In the gateway window the types carry the same names as in the browser under Scan › Credentials, for instance User Account, SSH Access and Entra ID App.

​
Finding the entry again in the browser

Under Scan › Credentials the new entry appears with the Storage Location Gateway—but read-only: the row cannot be selected, and a click on it shows only a notice instead of a form. Editing and deleting stay reserved for the gateway window the entry came about in. When editing, password and key are empty and must be entered again. The entry can only be used in jobs that run on exactly this gateway—for every other gateway and every other job it stays invisible, no matter which type it carries.

​
Deleting

Delete in the Credentials tab asks back and names the entry: “The credentials ’…’ will be deleted, including their key in Docusnap365. Delete them?” After Delete the local file and the key are removed, and the entry disappears there and in the browser.
Deregistering the gateway deletes all credentials stored on the gateway in one go. The confirmation before deregistering announces this; there is no confirmation per entry, see Installing and Registering the Gateway. The same applies when the gateway is deleted under Scan › Gateways, see Managing Gateways. A single entry cannot be restored afterwards.

​
What sets the local route apart from the central one

The difference lies in what Docusnap365 gets to see. With a central entry the encrypted secret leaves the network and sits in the vault of Docusnap365. With a local entry the encrypted file stays on the gateway; in the cloud there is only the—itself encrypted—key to it, together with a record without secrets.
A local entry also needs the connection to Docusnap365, because its key is stored there. Without the connection it can neither be created nor read nor used in a job.
If several gateways need the same access, we create the entry on each of them individually—a local entry applies only to the gateway it came about on.

​
What’s next

For the day-to-day management of the gateway see Managing Gateways. For assigning credentials while creating a job see Creating a Scan Job.