REST API auth error

[BayWa IT Workplace Atlassian]

Hi Community,

we´re building simple Python scripts for JIRA using the REST API with Basic auth (this way is ok for us, no need for Oauth at the moment).

For building the correct codes we´re using SOAP UI before we implement it in our scripts.

When we start execution, for example GET on https://jira.ourdomain.com/rest/api/2/applicationrole we see an error 401 Unauthorized (401). After some tries we get an error 403 and CAPTCHA is active for this user .

So it´s seems that data was correct and the username can be extracted from base64 encoded string by JIRA (base64 string is username:password).

In the past this way worked fine.

The same credentials (base64) work perfect in Confluence with REST API, so it seems to be a problem on JIRA side. In the backend both systems use Crowd with the same user directory (LDAP).

We´re using JIRA 8.6.1 with reverse proxy and activated SSL.

Regards

Uli

[Jobin Kuruvilla [Adaptavist]]

On the edit mode, it will show only user name. But you can still search using Full name. You cannot change it without modifying the javascripts etc.

On the view mode, it will show full name with a link to the profile. That is the expected behavior.

[CIMB Bank SG IT Service Management Team]

Hi Jobin,

Thanks for the nifor, is there a way to change the core java script for User Picker field to show both user name and user full name? just like Reporter and Assignee field?