Vault Send
Passwords in the ticket, without leaving the password in the ticket
Vault Send adds a Secure credential button next to Add, in the ticket reply. The technician types the login and password, the browser encrypts everything before sending and the reply gets a link that only opens for the time and the number of views you choose. The password stays out of the ticket history, the notification email and the GLPI database. Free, for GLPI 10, 11 and 12, with your company's Vaultwarden.
FreeGLPI 10, 11 and 12
Features
The link uses Bitwarden Send, stored in your Vaultwarden. The recipient opens a page with an explicit button, which email link scanners cannot use up, and sees the credential straight from the vault. If a password was already typed in the reply, GLPI warns before sending and swaps those lines for the secure link.
No vault yet? NexTool deploys Vaultwarden on your server, hosts a vault for you or keeps the one you already have updated and supported.
How it works
Step 1
Connect Vaultwarden
In Vaultwarden, create a user just for GLPI and copy its API key. In the Vault Send Connection tab, enter the vault address, the Client ID and the Client Secret and test the connection.
Step 2
Grant the profiles
In Administration > Profiles, NexTool tab, give technicians the right to send credentials and, if you want, self-service requesters too.
Step 3
Send it in the reply
In the ticket reply, click Secure credential, fill in the login and password, choose the expiry and views and insert. The link goes into the text and is sent with the reply, through the usual Add button.
See it in action
A quick tour of what the plugin does in practice.
Video demo coming soon.
Image gallery
1 / 1
Frequently asked questions
Is Vault Send free?
Yes. The module is free and works on GLPI 10, 11 and 12, with the NexTool plugin 6.35.0 or newer. It uses your company's Vaultwarden.
Do I need a Vaultwarden?
Yes. The link is created with the Send feature of a Vaultwarden that the GLPI server can reach, using a service account just for GLPI. If you don't have one yet, NexTool deploys it on your server or hosts a vault for you.
Does the password go through the GLPI server?
Not in clear text. The browser encrypts the login and password in the Bitwarden Send format before sending: GLPI receives only the encrypted text and passes it on to the vault. The key that opens the content travels only in the link, after the #, and never reaches any server.
What if someone else opens the link first?
The link is valid for the time and number of views you chose. With a single view, any improper access uses up the link and the recipient notices right away: you revoke it and send another. The optional access password stops anyone who has only the link, such as bots that open links.
Does GLPI need to run on HTTPS?
Yes. Encryption in the browser only works over a secure connection, so GLPI must be accessed through HTTPS.
Can requesters send a password too?
Yes, if the self-service profile has the module's right. A requester's reply is always public, so the technician can see it.
No vault yet?
NexTool deploys Vaultwarden on your server, hosts a vault for you or keeps the one you already have updated and supported.
Talk to our teamStart using Vault Send
View available plans or read the full article about this module.