Use the Integration With Jira

StrongDM’s integration with Jira, when paired with the Access Workflows feature, allows you to browse the StrongDM resource catalog and request access to resources within Jira. It also provides a way for approvers to initiate StrongDM workflows to approve access requests. This integration gives you the ability to easily request access to the resources you need without opening another application.

This guide describes how to use the integration with Jira to request or approve access. To learn about configuration of the integration within your Jira workspace, see Set up and Configure the Integration With Jira.

Request Access #

Although Jira Service Manager (JSM) is a typical use case for the integration, it also works with other projects. If StrongDM is enabled on non-JSM projects, the access request fields are available on issues in that project as well, and values can be added or modified anytime until the issue reaches the status that triggers the access workflow in StrongDM.

To request access to resources, use the following steps.

1. Go to the Jira portal for the project in which you’d like to make a request. This is often a service desk for your organization.
2. If this is a project with StrongDM enabled, there are StrongDM access request options in the JSM request form (or in the issue itself if directly editing issues). The StrongDM fields in the form are:
   • Request access on behalf of StrongDM user: If this is a request for you, pick your name. If this is a request made on behalf of another StrongDM user, choose that user. This field is only present for users with the “modify reporter” permission in Jira. Without that permission, this field is not present, and the StrongDM user is automatically matched to the Jira user creating the request or issue.
   • Resources: This is a list of resources that are available for the StrongDM user to request access to.
   • Duration and Unit: These fields are for setting a number for duration and a unit of time, such as “30” and “Days”.
   • Start date: This field is optional and can be set if you do not want the access period to begin immediately.

Once the request ticket is sent, it is reviewed like any other ticket to a Jira service desk. If it is given the appropriate status (often completed or resolved), the access is requested and automatically approved within the StrongDM system.

Approve Access Requests #

To resolve access requests made via Jira, the approver should move the Jira issue into the state that triggers the integration, often “Resolved”, “Completed”, or similar. The actual StrongDM access request does not occur until this happens, at which point the access request is generated and automatically approved within StrongDM.

Once an issue is moved to the status that triggers approval, the request is made and approved, and that is the end of the StrongDM interaction with Jira for that issue. The end user’s StrongDM access doesn’t change if the issue is moved to another status or moved back into the approval-triggering status. The interaction begins and ends the moment it is put into the approval status that was chosen in configuration.