Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Will GDPR Changes to the api impact project urls?

Dylan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 15, 2019

Hi, I'm looking at how best to be compatible with the changes to the rest APIs, and have been reading https://developer.atlassian.com/cloud/bitbucket/bbc-gdpr-api-migration-guide/. I am confused about how (or if) this will impact endpoints with the owner in the url For instance, the example given on that page for issues is " https://api.bitbucket.org/2.0/repositories/testingtheteammodel/foobar/issues/1/changes", but it also states that */{username}/*  will be replaced with the uuid/account_id. Does this mean the example is incorrect, or are there other endpoints that are exempted from uuid/account_ids?

Also, am I correct in assuming this won't impact repo urls?

1 answer

0 votes
Stephen Sifers
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 18, 2019

Hello Dylan,

Thank you for describing what you’re seeing and expecting as a result of the GDPR changes.

The reference you have posted is an example API URL to give you an output result which shows the change. This looks to be a possible error in the formatting of the URL, and I will submit a change request to have it reviewed and changed.

As far as usernames being removed and changed to account_id, the document you referenced states the following:

Changes to how users are identified: Personal data that is used to identify users, such as the username will be removed from the REST APIs. Users will be identified by their Atlassian account ID (account_id) instead. You can also continue to use the uuid for the user account.

 

Changes to the visibility of user information: Users will be able to restrict the visibility of their personal data through their user profile privacy settings, or in the case of a managed account, the visibility settings that are decided by the site administrator. This means that fields such as display_name will return different values based off the privacy settings of the target user and the relationship between the requesting user and the target user.

Requests that use username to identify accounts in API request objects will now use the account_id

Source documentation: Migration guide for major changes to Bitbucket Cloud REST APIs to improve user privacy

The above statement points out that any reference to username will be changed to account_id.

I hope this helps to clarify what is being replaced with account_id within the REST API.

Regards,
Stephen Sifers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events