---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Onboard JFrog using Classic

# Onboard JFrog to DevOps Change Velocity --- Classic {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Connect to an instance of the JFrog artifact tool to enable you to track artifacts published to JFrog.

## Before you begin

Role required: sn_devops.admin or sn_devops.tool_owner

Complete the steps specified in the [Getting started](https://servicenow-prod.fluidtopics.net/zYfXM71OMizgQDlC6XiIiA "Learn about the setup process for DevOps Change Velocity that is required before configuring integrations with your toolchain.") section before connecting to a tool.

## Procedure

1. Enter the JFrog instance details to connect to DevOps Change Velocity by navigating to AllDevOpsToolsCreate New (legacy).
2. Enter a value in the Tool Name field and fill in the tool details.  
   {#devops-jfrog-create-tool__table_jfq_lwn_2tb__entry__2}

   | Field | Description |
   |-|-|
   | Tool integration | Tool to integrate. In this case, select JFrog. |
   | Tool URL | URL of the existing JFrog instance to integrate. |
   | Tool username, Tool password / Access token | Login credentials of the global admin for the existing JFrog instance. |
   [Table 1. Create DevOps Tool form]

   {#devops-jfrog-create-tool__table_jfq_lwn_2tb}

   For a list of all the permissions required on the credentials for connecting to JFrog, see JFrog permissions in [Permissions required for DevOps tools](https://servicenow-prod.fluidtopics.net/rkQZOOxQSNdDZ7d5eHch0A "Permissions required in your third-party tool to connect to DevOps Change Velocity.").
3. Select MID Server for an on-premises tool that is attached to a MID Server.  
   Application is automatically set to DevOps and capability is set to REST.
4. Click Submit.  
   Note:  
   If your tool credential has changed, you must update the credentials in your ServiceNow instance. For more information, see [Update third-party tool credentials in DevOps Change Velocity](https://servicenow-prod.fluidtopics.net/W3H0I3eiOCLVglPK635qzA "If your tool credential has changed, you must update the credentials in your ServiceNow instance to avoid getting disconnected.").  
   If the connection is successful, the tool is created in ServiceNow and connected to your JFrog instance.

On successful tool creation, you're taken to the tool record page.

5. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field on the Access tab.  
   The tasks the users in the groups can perform depends on the roles assigned to them.
   * DevOps Tool Owner role: Can view and edit the tool.
   * DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
   * DevOps Administrator role: Can edit all tools.
   * Other DevOps roles: Can view the tool.

   {#devops-jfrog-create-tool__ul_qnp_fkx_5wb}  
   Note:  
   Only groups containing users with DevOps roles are available for selection in the Maintained by field.

   The All App Owners can view and associate tool objects to applications option becomes available for selection if you choose to restrict access to the tool. This option enables all users having the DevOps App Owner role to access the tool. If selected, they'll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.

*[\>]: and then