ideaport.blogg.se - Sourcetree change password for repository

#SOURCETREE CHANGE PASSWORD FOR REPOSITORY PASSWORD#
#SOURCETREE CHANGE PASSWORD FOR REPOSITORY WINDOWS#

If this does not help, continue with the next step.

#SOURCETREE CHANGE PASSWORD FOR REPOSITORY WINDOWS#

Make sure that SmartGit’s executables (on Windows all files in the bin\-subdirectory) are not blocked from opening a local socket or connecting to a local socket.This can been seen in the injector log files which will show up a. Once invoked by Git, this tool is connecting to SmartGit using sockets to receive credentials.įirewalls/Antivirus tools may block this socket communication.

#SOURCETREE CHANGE PASSWORD FOR REPOSITORY PASSWORD#

SmartGit is configuring Git with a small utility tool for password callbacks. If it still does not work, leave AutoRun~ renamed and restart with step “ Check Command”.If it works now, consider to permanently disable the AutoRun script or enable Git’s credential manager.Otherwise, temporarily rename the AutoRun script to AutoRun~ and see whether authentication works now.If not configured, continue with the next step.Open the Windows registry and check whether for key HKEY_CURRENT_USER\Software\Microsoft\Command Processor the value AutoRun is configured. continue with step “Check Firewalls/Antivirus tools”.Ĭommand Processor AutoRun scripts may interfere with SmartGit’s authentication hook.if you are on Windows, continue with the next step.If you are not connected to a hosting provider.If your repository is connected to GitHub, check whether this problem might be related to organization access.If the command does not work without the hosting provider configured, continue below.if it stops working again, continue with step “Contact Support”.

If the command works there, re-setup the hosting provider in the Preferences again and retry.

If your repository is connected to GitHub, Bitbucket or another hosting provider, known to SmartGit, open the Preferences, select section Hosting Provider and get rid of the corresponding hosting provider there.

SmartGit’s Hosting Provider configuration may interfere with the authentication.

continue with step “Check Environment Differences”.

if you are on Windows, continue with step “Check Git Credential Manager”.

If the command works there, continue with step “Check Hosting Provider”.

Open a Git shell from within SmartGit: right-click the offending repository in the Branches view and invoke Open Git-Shell and try to invoke the command from this shell.

If they are definitely correct, continue with step “Check Credential Manager”.

Otherwise, check whether the access URL is actually correct and your credentials are correct.

If the command works there, continue with step “Check Git-Shell”.

On Windows, you will usually just invoke cmd.exe from the Start-button.Įrror: Authentication failed for ‘…’ Step “Check Command”Ĭheck the Output view or the log-directory for the exact command which fails and try to invoke the command from an independently opened terminal/shell.

While resolving authentication-related problems, it’s recommended to disable Detect remote changes option in the Preferences, section Background Commands to prevent background operations spoiling the log file with too many problems.Īn independently opened terminal/shell refers to a terminal/shell which has not been opened through SmartGit:

Log denotes directory inside the Settings Directory containing SmartGit’s log files. This is a collection of common problems and resolutions related to authentication.