$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Being an Atlassian Connect add-on, Pathfinder collects some data to its database that is stored outside of your OnDemand instance. All communication between your JIRA and Pathfinder is made over HTTPS (encrypted with SSL). There is very minimal data collected by Pathfinder though all Atlassian Connect add-ons require to collect these in order to correctly associate the requests made to the add-on to the correct JIRA OnDemand instance. For all details about these requirements, please read Atlassian's document on Atlassian Connect add-ons design considerations. The data collected is sent by the JIRA instance, common to all of its add-ons developed using the Atlassian Connect architecture. The data elements collected are the following:

  • The base URL of your OnDemand instance (e.g. 'https://greffon.atlassian.net')
  • The description of your OnDemand instance (e.g. 'Atlassian JIRA at https://greffon.atlassian.net')
  • The key of the add-on uniquely identifying your OnDemand instance (e.g 'greffon.atlassian.net')
  • The name of the instance ('JIRA' or 'Confluence')
  • The public key of your (an RSA public key used for communication between the add-on and JIRA OnDemand)

At this time, no other information is stored to Pathfinder. It is possible that in the future we add features to Pathfinder that would require persisting other data, such as user preferences. No sensitive data will ever be persisted to Pathfinder's database. Any modification to the set of data collected will be communicated to the users before new versions of Pathfinder are made available for installation.

  • No labels