Forums

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

API Changes - Alternative to using username?! Breaks my integrations

Morten Stensgaard
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!
August 10, 2018

Hi Atlassian community

 

Major API changes are arriving: https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/

 

And this will break our integrations between systems

 

Reason: We lookup users in JIRA based on AD account firstname.lastname

GET https://jira.atlassian.net/rest/api/2/user/search?username=firstname.lastname

 

But if username is deprecated on the APIs, how can we even get the unique identifier(AccountID) based on AD details?

 

As JIRA Admin my service account needs to be able to lookup JIRA users based on information I already have in my AD(SAML/UserID)

 

If this is not possible, I would have to MANUALLY maintain a mapping list between JIRA and my other systems = Waste of time every single time a new users gets onboarded!

 

As an Atlassian admin, it would be nice to have some kind of simple control of the mapping/lookup between JIRA and other systems based on simple existing information like firstname.surname or emailaddress.

 

So will there be any exceptions to JIRA(ex ADMIN account) on the API for service/integration account usage?

 

Thanks in advance

/Morten

0 answers

Suggest an answer

Log in or Sign up to answer