This pull request addresses the issue of creating a basic account pairing between Latch and Jira, as outlined in issue #5. The existing application in the repository is outdated, and this PR introduces a new implementation compatible with Jira Marketplace or Jira Forge.
Key Changes
New Directory: All new implementations are organized under the /JiraMarketplace directory.
Authentication: Implemented the Latch API authentication process, which involves signing requests using a simplified two-way OAuth protocol. This includes generating the Authorization and X-11Paths-Date headers as per Latch's requirements.
Pairing Process: Added functionality to pair accounts using a token obtained from the user's mobile app, following the Latch API's guidelines.
Impact
These changes are foundational for integrating Latch's authentication and pairing capabilities with Jira, setting the stage for further development and enhancements. The implementation ensures secure communication with Latch's API, which is crucial for maintaining data integrity and user trust.
This PR fixes #5 by laying the groundwork for a modernized application that aligns with current standards and requirements.
This pull request addresses the issue of creating a basic account pairing between Latch and Jira, as outlined in issue #5. The existing application in the repository is outdated, and this PR introduces a new implementation compatible with Jira Marketplace or Jira Forge.
Key Changes
/JiraMarketplacedirectory.AuthorizationandX-11Paths-Dateheaders as per Latch's requirements.Impact
These changes are foundational for integrating Latch's authentication and pairing capabilities with Jira, setting the stage for further development and enhancements. The implementation ensures secure communication with Latch's API, which is crucial for maintaining data integrity and user trust.
This PR fixes #5 by laying the groundwork for a modernized application that aligns with current standards and requirements.