Closed agagelis closed 1 year ago
Hi @agagelis, the token length would make no difference. It's just a string as far as the code is concerned.
The 403 would suggest that the server hasn't been configured for REST calls.
Could you try something like this in a private browser window:
https://192.168.0.120:9283/rest/api/2/user?username=gnl
and see what you get back?
thanks George
Hello George,
It seems that you are right. Here are my results. and after changing username with accountId..
On the other side.. this URL is working correctly: https://**COMPANY**.atlassian.net/rest/agile/1.0/board !!!!
I made it work . I just had to use the API token as password and NOT select the "use Access Token" checkbox!!!!
So I am closing the issue! Thanks for your support!
Sigh, right. Jira Cloud uses the token in a different way than Jira 9
I am trying to connect to my Jira repository (on Cloud) but this exception is thrown:
me.glindholm.connector.eclipse.internal.jira.core.service.JiraException: java.util.concurrent.ExecutionException: RestClientException{statusCode=Optional[403], ErrorCollections=[ErrorList [status=403, errorMessages=[], errors={}]]}
I also tried to connect with my redentials, and could not succeed either. Eclipse Version : 2022-12 (4.26.0)
Is there any chance , the problem is due to this...??