This article offers an in-depth examination of the PassMan Password Manager app, including a detailed tutorial on its optimal use. It covers secure methods for storing and sharing credentials within Jira tickets through PassMan's browser extension. Additionally, it explains PassMan’s advanced password management capabilities such as storing, managing, sharing and monitoring of sensitive information beyond Jira. All this within a dedicated business vault, ensuring secure and efficient handling of credentials.
Open PassMan Password Manager Vault
Navigate to the Apps menu in the top navigation bar, select the PassMan app.
If you haven't configured PassMan yet, begin with the steps outlined on the Configuring the app documentation page.
A window will pop up where you need to click on the Login to PassMan button. Wait a few seconds as the system logs you into the vault. PassMan needs access to your Atlassian account. To start using PassMan, you must accept this by clicking on the Accept button.
Voilà, you are now inside the PassMan Corporate Password Manager!
Now, you have a safe place to store, manage, share and track all your business secrets.
| Info |
|---|
Please note that PassMan is a Jira-integrated vault which can also be used as a standalone app, meaning it has features specifically designed for use within Jira, while other features can be used independently of Jira. For simplicity, we have divided the guide into two parts on this page. b. Features in PassMan Password Manager |
.png?version=1&modificationDate=1719914004210&cacheVersion=1&api=v2&width=556)
Settings / Features in PassMan
Settings / Features in Jira
1. Get the browser extension
To utilize PassMan's Jira-specific features, first download the appropriate PassMan Secure Login browser extension from PassMan’s website.
PassMan Secure Login extension is currently available for Chrome, Edge, Firefox (Safari coming soon) browsers.
In the top right corner of your browser, upon successful installation, a PassMan icon will appear.
It will be highlighted in red, indicating that you are not logged into PassMan yet.
This is because you haven't connected your existing password vault to the browser extension.
Click on the icon, and in the popup configuration window, enter the URL of your password vault (return to the PassMan page and copy the URL).
On this configuration page, you can also perform advanced settings. For more details, you can read about it in the Comprehensive Documentation covering PassMan's standalone functionalities.
Now, go back to your Jira.
2. Insert secure login-links
No need to store plain text passwords in Jira tickets anymore.
With PassMan, you can insert secure login links in Jira comment and description fields, or in Confluence.You can securely store and share passwords (SSH keys, certs) in Jira tickets using super secure login links instead of storing plain text passwords. With just a few clicks, you can add credentials to a ticket's description or comment fields, ensuring easy access to all business targets for your team!
Open end start editing a Jira ticket and navigate to it’s comment or description field.
Right-click to display the browser context menu.
Navigate to PassMan Passwords… menu item.
Select the Insert 1click link option from the contex menu.
Afterwards, a window will pop up. Click on the Find passwords manually option.
Choose any username-website pair that you would like to share with your teammates, or assign with a ticket and store it in the description or comment field.
The result will be in this format: <website or host name> / <username>
3. Use secure login links
Normal users will only see a link to access the <website or host name> and the associated <username>.
Clicking on the link will automatically log the authorized user into the website or target system.
Access to the provided link is contingent upon proper authorization.
Confidential data stored in PassMan can only be accessed by users (Jira user) or groups (Jira group) with appropriate permissions.
Users without access rights will receive an error message indicating their inability to access the data.
