btp trial abapGit pull/push, HTTP401

[fvlabq]

Hi,

I'm having the same problem when trying to pull/push abap source codes in BTP trial via abapGit.

I use GitHub personal token already but it always say: "Unauthorized access to resource(HTTP 401). Check your credentials"

Could anyone help, please?

P.S.

There is the same question raised https://answers.sap.com/questions/13820753/btp-trial-abapgit.html?childToView=13848184

[fvlabq]

- I can't pull/push source codes from BTP trial on eclipse with abapGit to either public/private repository. It always says Unauthorized access to resource (HTTP 401). Check your credentials. I have tried again and again many times, with various internet access, but the problem persists. I also tried to regenerate new GitHub tokens as well.

- HOwever, if I download the full abap source code of abapGit (more than a hundred thousands of lines of code) to activate and run it on SAP GUI, it works like a charm. as I can map private repositories from my GitHub to any package desired. NOte that for SAP GUI I installed ABAP AS NetWeaver trial.

[fvlabq]

local server with NetWear, it's working fine

[ArneVH]

Hi Luan,

Did you ever find a solution to this?

I'm facing the exact same problem at the moment: working on-premise, not working from BTP..

Kr,

Arne

[fvlabq]

Hi Arne,
Please refer the recent instruction/suggestion from Shubham & Sadullah to see if the problem is gone.

I don't have access to the platform where the problem persisted that I raised the question so I can't check.

I hope it'll be worked out.

Thank you all!

Best regards,

Luan

[Sadullah]

Last week I was faced with same problem, because I entered my token wrong. After it, not worked and poped up a warning like yours. In my case as a solution I unlink the repo in eclipse and link again. That works for me. Also, if you connect to a on-prem system in eclipse, you need to increase code line range (300000 lines) in eclipse which it is 45000 by default.

[shubham_waghmare]

This issue occurs because of an expired personal access token(PAT) that is stored in secure store of eclipse. While staging, this expired PAT is used for authentication, which fails and leads to 401 error.

This issue has been fixed with abapGIT ADT client version 1.7.2. With this, users get the staging credentials dialog to enter a valid PAT in case the PAT is expired.

Please update the abapGIT version using the following update site: https://eclipse.abapgit.org/updatesite/.

[shubham_waghmare]

Note: Fine-Grained PATs from Github are not supported yet.
Please use classic PATs.