Skip to main content
Announcements
A fresh, new look for the Data Integration & Quality forums and navigation! Read more about what's changed.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Not able to connect to Talend Studio Git Repository

Hi,

 

I joined a new (new to me, running already) Talend project where Git used as a source control.

 

I am using Talend version 6.3 , Subscription one. 

In TAC I have configured my Git credentials. 

In the project configuration it has got the administrator's credentials configured at TAC.

 

I have configured the connection details in Talend Studio  and after I chose the existing project there is a prompt for Git password, When I enter my password I get an error like this.

 

What could be the reason? 

 

I have checked logging into the git website and I am able to access repository. I am able to log in TAC as well. 

 

 

org.talend.commons.exception.PersistenceException: Can not connect to project with url "<url>".
	at org.talend.repository.remoteprovider.RemoteRepositoryFactory.delegateBeforeLogon2(RemoteRepositoryFactory.java:376)
	at org.talend.repository.remoteprovider.RemoteRepositoryFactory.delegateBeforeLogon(RemoteRepositoryFactory.java:328)
	at org.talend.repository.remoteprovider.RemoteRepositoryFactory.beforeLogon(RemoteRepositoryFactory.java:267)
	at org.talend.core.repository.model.ProxyRepositoryFactory.logOnProject(ProxyRepositoryFactory.java:1850)
	at org.talend.repository.ui.login.LoginHelper$1.run(LoginHelper.java:429)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Caused by: org.talend.commons.exception.PersistenceException: username or password are not correct, please check in TAC users configuration
	at org.talend.repository.gitprovider.core.GitProjectUrlCheck.check(GitProjectUrlCheck.java:95)
	at org.talend.repository.remoteprovider.RemoteRepositoryFactory.delegateBeforeLogon2(RemoteRepositoryFactory.java:374)
	... 5 more
Caused by: org.eclipse.jgit.api.errors.TransportException: <url> not authorized
	at org.eclipse.jgit.api.LsRemoteCommand.call(LsRemoteCommand.java:196)
	at org.talend.repository.gitprovider.core.GitProjectUrlCheck.check(GitProjectUrlCheck.java:89)
	... 6 more
Caused by: org.eclipse.jgit.errors.TransportException: <url> not authorized
	at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:501)
	at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:309)
	at org.eclipse.jgit.api.LsRemoteCommand.call(LsRemoteCommand.java:175)
	... 7 more

 

 

Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hello,

When did this start occurring? Do you use the Two-factor authentication for GitHub?

Could you please try to clear the Talend Administration Center (TAC) cache to see if it works?

https://community.talend.com/s/article/HOWTO-Clear-the-Talend-Administration-Center-TAC-cache-sZU9L?...

Best regards

Sabrina

View solution in original post

8 Replies
Anonymous
Not applicable
Author

Hello,

Are you creating a private git project?

Have you tried to update password on TAC side , use the correct one and re-launch studio to see if it works?

Best regards

Sabrina

 

Anonymous
Not applicable
Author

I guess there was a space at the end of my username, once I removed that solved the problem

 

It would be much better if we have a test connection button in TAC to verify the Git connection details are correct.

 

Cheers!
Gatha

the_etl_guy
Contributor

Hi,

May I please know how this was fixed? All my TAC to Github connections are working fine. The first time I created project in Studio, it worked and I could see all branches and code but after restarting studio all branches have disappeared..shows only master in dropdown and log says below:

 

!MESSAGE 2023-07-28 11:16:23,339 ERROR org.talend.commons.exception.CommonExceptionHandler - https://github.com/YYYY/XXXX.git: not authorized

Anonymous
Not applicable
Author

Hello,

We need a little bit information to address your issue.

Could you please clarify in which Talend version/edition you are? Any patch installed? Is there any more error message in your log?

Best regards

Sabrina

the_etl_guy
Contributor

Hi Sabrina,

 

It's 7.2.1

Patch: Patch_20210129_TPS-4616_v1-7.2.1.zip

 

More of the logs:-

 

!ENTRY org.talend.platform.logging 4 0 2023-07-28 11:16:23.340

!MESSAGE 2023-07-28 11:16:23,339 ERROR org.talend.commons.exception.CommonExceptionHandler - https://github.com/YYYY/XXXX.git: not authorized

 

!STACK 0

org.eclipse.jgit.api.errors.TransportException: https://github.com/YYYY/XXXX.git: not authorized

at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:222)

at org.eclipse.jgit.api.LsRemoteCommand.call(LsRemoteCommand.java:161)

at org.talend.repository.gitprovider.GITProviderService.getShallowCloneBranches(GITProviderService.java:341)

at org.talend.repository.gitprovider.GITProviderService.getBranchList(GITProviderService.java:212)

at org.talend.repository.RepositoryService.getProjectBranch(RepositoryService.java:906)

at org.talend.repository.ui.login.LoginHelper.getProjectBranches(LoginHelper.java:788)

at org.talend.repository.ui.login.LoginProjectPage$22.run(LoginProjectPage.java:1850)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Caused by: org.eclipse.jgit.errors.TransportException: https://github.com/YYYY/XXXX.git: not authorized

at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:544)

at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:362)

at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:200)

... 7 more

 

 

 

Thanks!

Anonymous
Not applicable
Author

Hello,

When did this start occurring? Do you use the Two-factor authentication for GitHub?

Could you please try to clear the Talend Administration Center (TAC) cache to see if it works?

https://community.talend.com/s/article/HOWTO-Clear-the-Talend-Administration-Center-TAC-cache-sZU9L?...

Best regards

Sabrina

the_etl_guy
Contributor

Hi Sabrina,

 

No we don't use 2FA but clearing the TAC cache did the trick.

 

Thanks!

Anonymous
Not applicable
Author

Hello,

Great it helps and feel free to let us know if there is any further help we can give.

Best regards

Sabrina