Proxy User

    A proxy user is a work management system user, who will be used by Exalate to make changes, such as:

    • Creating issues
    • Updating data

    The proxy user impersonates external instances. All changes on local issues are performed on behalf of this user. You can use an existing user account or create a new one, specifically dedicated to Exalate.

    Changes made by the proxy user will not be synchronized.

    If you set the administrator as a proxy user and create issues with the help of the 'create on behalf of ' Service Desk functionality, issues will not be synchronized.

    The proxy user configuration is different for each work management system. 

    Azure DevOps

    Access to Azure DevOps Exalate Console (Log-in)

    Exalate needs to authenticate to the Azure DevOps instance. You can provide such access using the Personal Access Token(PAT).

    Use the PAT to access the Exalate admin console. Check out How to generate the PAT(Personal Access Token) in your Azure DevOps instance.

    Proxy user in Azure DevOps

    The proxy user is the Azure DevOps user account that fetches information from the Azure DevOps instance and updates Work items with incoming changes.  
    The configuration of the proxy user takes place during the first installation of Exalate.  The user that is installing Exalate automatically becomes the proxy user.
    You can change the proxy user when the app is installed and running. To do so navigate to Exalate Menu Panel → General Settings → Configure and enter the PAT of the new proxy user.

    Proxy User Permissions in Azure DevOps

    The proxy user must be a Project Administrator and a member of the Project Collection Administrator group on the Organization level

    You can add the Project Administrator to the Project Collection Administrator in your Azure DevOps under Organization Settings → Permissions → Project Collection Administrators.

    GitHub

    Access to GitHub Exalate Console (Log-in)

    Use a personal access token to log in to Exalate for GitHub. The token needs to have access to private repositories with the repo scope.

    Proxy User in GitHub

    By default, Exalate for GitHub Proxy User is the repository admin or the organization owner, who is installing Exalate.
    The proxy user configuration takes place during the first installation of Exalate. The user that installs the app automatically becomes a proxy user.
    The proxy user must have a Personal Access Token with authorization to private repositories with the repo scope.

    Read how to generate a personal access token in GitHub: How to generate an access token.

    Proxy User Permissions in GitHub

    The proxy user has the same permissions as the admin or the organization owner in GitHub.

    HP ALM/QC

    Access to HP ALM/QC Exalate Console (Log-in)

    Log in to the Exalate app admin console with the credentials of the HP ALM/QC admin user. This can be a user you set up during the first configuration of the Exalate app for HP ALM/QC.

    Proxy user in HP ALM/QC

    You can set up a proxy user while your first-time Exalate configuration. The proxy user can be changed later on in the General Settings.
    To change the proxy user, navigate to Exalate Menu Panel → General Settings → Configure.

    Proxy User Permissions in HP ALM/QC

    The user should have administrative permissions to be able to see all the HP ALM/QC projects and user field configurations.

    For more information about user permissions in HP ALM/QC check HP ALM/QC documentation.

    Jira Cloud

    Proxy user in Jira Cloud

    The proxy user in Jira Cloud is the app user that is being created automatically. This user cannot be modified. The username is Exalate and the email address is com.exalate.jiranode@connect.atlassian.com.
    The proxy user in Jira Cloud is a member of the following user groups: 

    • atlassian-addons
    • atlassian-addons-admin
    • jira-core-users
    • jira-servicedesk-users
    • jira-software-users 

    At the moment, there is a security vulnerability in Exalate, that lets you access private project data with the Connect operation. We recommend making sure, that the proxy user has access only to public projects.

    For more info, check Security Vulnerability — You can access restricted project data with the Connect operation.

    Proxy User Permissions in Jira Cloud

     Jira Cloud grants correct permissions to apps through the atlassian-addons-project-access role. It is done after installing or updating an app. Jira Cloud also checks the permissions of existing apps across all Jira and Jira Service Desk projects and grants them the correct permissions.

    If you want to ensure that the app has no access to the project - remove the group from the corresponding permission in the permission scheme.

    For more details, check out Atlassian documentation

    Jira on-premise

    Proxy user in Jira on-premise

    By default, the proxy user is the user who installs Exalate. You can change the proxy user by navigating to Exalate Menu Panel → General Settings → Configure.

    At the moment, there is a security vulnerability in Exalate, that lets you access private project data with the Connect operation. We recommend making sure, that the proxy user has access only to public projects.

    For more info, check Security Vulnerability — You can access restricted project data with the Connect operation.


    Proxy User Permissions in Jira-on premise

    In Jira on-premise, the proxy user needs to have the following permissions:

    • Browse Project
    • Create issue
    • Edit issue
    • Link issue
    • Transition issue: change statuses (on issue transition)
    • If comments are synchronized, the proxy user will need to add, edit, and delete a comment
    • If attachments are synchronized, the proxy user needs to add, and delete attachments
    • If work logs are synchronized, the proxy user needs to add, edit, and delete work logs
    • If security levels are synchronized, the proxy user needs to access the security levels
    • If you're using a trigger the proxy user must be able to search for issues

     In Jira Service Management, the proxy user needs to be a service desk agent.

    Salesforce

    Proxy user in Salesforce

    In Salesforce, the user that is installing Exalate automatically becomes a proxy user. 

    ServiceNow

    Access to ServiceNow Exalate Console (Log-in)

    You can access the ServiceNow instance in one of these ways: 

    Basic login:
     In order to log in you use a Username and a Password. Exalate will not store the password in the database, but use the rest connection to attempt to log in to the ServiceNow node.
    OAuth token:
     Authentication with a Username and an OAuth token. Exalate will store the token and use it to access it. The token is refreshed every time the lifespan ends.

    OAuth token can be used as long as the refresh token is valid. Read more about setting up the refresh token in the article Access the Exalate app in ServiceNow.

    You need to generate a new refresh token after the old one is expired. We suggest setting a longer lifespan for the refresh token.

    Proxy user in ServiceNow

    To change the proxy user in Exalate for ServiceNow:

    1. Log in to the Exalate admin console.
    2. Navigate to General Settings.
    3. Input details:
      • Servicenow instance URL.
      • Proxy user name.
      • Proxy user password.

    Proxy user permissions in ServiceNow

    Users and Permissions

    For security reasons, it is better to create a separate role with specific permissions for a proxy user instead of giving him an administrator role.

    To integrate Exalate with ServiceNow you need 2 ServiceNow user accounts:

    Proxy User
    The ServiceNow user account that fetches information from the ServiceNow instance and updates the ServiceNow entities with incoming changes.
    The proxy user can integrate various tables or attributes depending on the permissions defined by his user role in ServiceNow.


    Exalate Console users
    ServiceNow user that is authorized to configure the Exalate app for ServiceNow. The Exalate console user must be an admin in your ServiceNow instance or the proxy user.

    Exalate uses REST API to communicate with the ServiceNow issue tracker. By default, ServiceNow REST APIs use basic authentication or OAuth to authorize user access to REST APIs/endpoints. Therefore, the Exalate console users must have access to the ServiceNow instance admin configuration.

    Role Management V2 REST API plugin must be installed and activated on your ServiceNow instance.

    Starting from the New York version this plugin is included by default. But if you've recently updated your ServiceNow instance to the latest version you need to activate Role Management V2 REST API plugin manually. ServiceNow contextual security.

    Zendesk

    Proxy user in Zendesk 

    By default, Exalate sets Zendesk instance admin as the proxy user during installation.

    Exalate requires a dedicated Zendesk admin as a proxy user.

    Proxy user permissions in Zendesk

    The proxy user can restrict the roles or groups that can access Exalate. It is possible to perform during the installation of the app or in the Apps and Integrations settings.