You can revoke the token on the Jira side using web UI). The a ccess token persists for 5 years unless revoked (no option to customize, as this policy is defined on the Atlassian side. Oauth 1.0.: Only the access token is used. We did not find any mention in Atlassian's documentation of how to limit the information to just a few fields.Ĭan we have a diagram showing the data flow between Jira and Miro, such as during authentication, normal usage, etc.?ĭetailed info can be found in this Jira Developers article. We implement our integration according to Atlassian documentation. let’s assume we only want to see the ‘title’ and ‘status‘, can we prevent access to other fields such as ‘description’ or ‘attachment’ to any user in Miro? Is there a way we can restrict the information that can be retrieved from Miro? Ie. Only the general Miro security protocols are applied. (Jira Server or Data Center) also, the data are updated if the webhooks are configured during the Jira Cards plugin setup process. Yes, Miro retains the card's data which are added to the board.įor OAuth 1.0. Will Miro retain any of the customer’s Jira data? If yes, how long is the retention period and how will the data be secured? We also support mutual TLS for Enterprise plan. It encrypts HTTP messages before transmission and decrypts messages upon arrival. Is data secured in transit between Jira and Miro? How does the Jira-Miro authentication work? Possible issues with Jira Cards and Jira Add-on.
0 Comments
Leave a Reply. |