FAQs - Azure DevOps - Integration

FAQs - Azure DevOps - Integration

Q1: Setting Up Least Privileged Security Settings for Azure DevOps Personal Access Token (PAT) Integration with Prolaborate 

Customer reported a query regarding setting up security settings for a Personal Access Token (PAT) in Azure DevOps for integration with Prolaborate. 

Reference

https://desk.zoho.com/agent/sixthforcesolutions/sparx-platform-support/tickets/details/759413000011757546 

First response – Troubleshooting Steps  

Hi Giedrius, 
Thank you for your patience, 
To create a PAT with the necessary permissions, please refer to the official documentation provided by Microsoft Azure DevOps. In the documentation, you will find details on how to create a PAT and set the required scopes to authorize specific tasks for your integration. Here's the link to the documentation:  
https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows 

When creating the PAT, it's crucial to select only the scopes that are essential for the integration to function correctly. In your case, you should limit the PAT's permissions to read and add information as needed for the DevOps-Prolaborate integration. By doing so, you can minimize the potential security risks associated with the token. 
 

 
 
If you have any specific questions or encounter any issues during the PAT creation process, please feel free to reach out, and we'll be happy to assist you further. 

Remediation 

Suggested the customer create a PAT by following the documentation provided by Microsoft Azure DevOps. Emphasized the importance of selecting only the essential scopes required for the integration (read and add information) to minimize potential security risks. 
 

Escalation Contact 

Product team if user asked more about PAT 
 

Reference Documentation 

https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows
 
https://prolaborate.sparxsystems.com/resources/v5/documentation/enterprise-architect-azure-devops-integration

    • Related Articles

    • FAQs - Microsoft Teams Integration

      Q1. We are not able to confirm if any data is collected while using MS Teams Plug-in for Proloborate. If so, what data do you collect? Answer The data stored from MS Teams do not contain Personally Identifiable Information (PII), However, MS Teams ...

    • Troubleshooting - Azure DevOps - Integration

      Q1. Setting Up Least Privileged Security Settings for Azure DevOps Personal Access Token (PAT) Integration with Prolaborate Customer reported a query regarding setting up security settings for a Personal Access Token (PAT) in Azure DevOps for ...

    • FAQs - Model Security Related

      Q1: Where the OpenID configuration will be stored, EA Client, Pro Cloud Server, or Repository? The OpenID configurations are stored in the repository and its respective database. Each repository needs its own individual configuration. To learn more ...

    • FAQs - JIRA

      Q1. Links generated from Jira Items are exposing the entire repository when accessed Answer This behaviour is intentional, as Jira provides only essential information, and users typically access Prolaborate to access comprehensive data. If you wish ...

    • FAQs - Discussions

      Q1: I wish to opt out of the discussion threads related to the Package 1 and be part of Package 2 only. Please share the steps to achieve the same. A:If your aim is just to be free from the notifications of discussions, you can enable the ...