I set up a svn server using svnserve to test how svn-git works.
When trying to dcommit I run into the problem that the tortoise gui does not give the option to choose the username, it just prompts for the password:
http://img1.uploadscreenshot.com/images/orig/11/31810164510-orig.png
Initially the username shown by the prompt used to be the windows authentication user (Razvan).
posting this as a temporary solution, if there is a better one I will accept it:
One solution would be to dcommit from command prompt and set the username:
git svn dcommit --username desiredusername
TortoiseGit will remember the username and password for future dcommits.
Related
I am trying to paste a Personal Access Token that I created in GitHub into the command line of a Ruby on Rails program I'm developing on Cloud9. I put in my GitHub username, and when I try to put in the PAT under password, it won't paste. I've tried with 2 different apps, but can't complete the git push. As a result I can't deploy my app to production.
I'm new at RnR, so have been learning using https://www.railstutorial.org/ following these instructions. I would appreciate any help I could get.
[website (main)]$ git remote add origin https://github.com/mhartl/hello_app.git
[website (main)]$ git branch -M main
[website (main)]$ git push -u origin main
After running the third command you will be prompted to enter your username and password. The username is simply your GitHub username, but the password is not your GitHub password; instead, the “password” must be a personal access token which you can create by following the instructions in the GitHub article “Creating a personal access token” I suggest selecting “No expiration” for the token expiration, and also be sure to select “repo” as the scope of the token so that it works at the command line. Once you’ve created and saved the personal access token, paste it in at the command line when prompted for a password to complete the git push
Check if it actually won't paste, meaning: when you paste a password, often it is not displayed at all: you get the impression the paste failed because nothing moved.
But do try, just after pasting, to click enter and the PAT should be taken into account, even if it remains "invisible".
Check also your git config --global credential.helper: a caching mechanism can help you not entering the PAT on each clone/push/pull operation.
At least, for instance, git config --global credential.helper "cache --timeout=86400"
You can see what is cached with:
printf "host=github.com\nprotocol=https"|git-credential-cache get
You can remove it with
printf "host=github.com\nprotocol=https\nusername=you"|git-credential-cache erase
You can store the new PAT with
printf "host=github.com\nprotocol=https\nusername=you\npassword=yourPAT"|git-credential-cache store
I'm facing problems while trying to pull/push my code into a GitHub repository using the cmd prompt for the last two days. How can I resolve this issue?
Logon failed, use Ctrl + C to cancel basic credential prompt. Username for 'https://github.com': satyendrasingh8 Password for 'https://satyendrasingh8#github.com': remote: Invalid username or password. fatal: Authentication failed for 'https://github.com/satyendrasingh8/chatApp.git/'
Fitz_Hoo is right! I just wanted to give a more detailed explanation that fix my issue. Essentially GitHub deprecated their password authentication recently (you can read more by clicking here).
Now instead of adding your username/email and password, you will login with your browser. The image below is the new interface. As Fitz_hoo mentions, you must update your Git to see the new changes!
If you are using Windows, you can simply use this command below to update your Git:
git update-git-for-windows
I fixed the problem just simply by upgrading my client Git Bash to the latest version!
When I encountered the problem, I received an email from a GitHub official, who told me the reason was mainly the Git version was incompatible:
GitHub has changed how users authenticate when using Git for Windows, and now requires the use of a web browser to authenticate to GitHub. To be able to login via web browser, users need to update to the latest version of Git for Windows. You can download the latest version at:
https://gitforwindows.org/
One reason for this message could be that the remote branch you were trying to pull was already deleted.
Delete the GitHub entry from Credential Manager: Control Panel → User Accounts → Credential Manager.
Then push the code again.
For me, the problem was that instead of my username I was trying to login with my email.
I received an email from GitHub telling me
We recently updated the format of our API authentication tokens,
providing additional security benefits to all our customers. In order
to benefit from this new format, please regenerate your personal
access token
I regenerated my personal access token (PAT) and was then unable to log in from command line on Windows 10 when I tried something like git pull.
A window would pop up, inviting me to enter 'username or email' and password. I tried various combinations, using the PAT, as mentioned in the GitHub documentation, and the actual password, but every time I received:
Logon failed, use ctrl+c to cancel basic credential prompt
Thanks to the answers from Fitz_Hoo and ousecTic, I updated my Git install with the command provided by ousecTic, and the authentication process was then completely different.
You can opt to use a PAT, but when you paste it in, no characters at all are shown, so just hit Enter.
In my case, I had this issue in relation to the federated authentication to AWS CodeCommit. The fix was to upgrade git to +v2.30.z (i.e. 2.35.3) and disable interactive prompt (docs):
git config --global credential.interactive false
A global configuration in ~/.gitconfig would look like:
[credential]
interactive = false
A AWS CodeCommit specific configuration, would look like (in ~/.gitconfig):
[credential "https://git-codecommit.us-east-1.amazonaws.com"]
interactive = false
here is the solution which works for me, uninstall Git from Machine after that install new version of it and sign in via web
I am on a Solaris 10 machine with opendj 2.4.5 installed. I am attempting to set a user's password with the ldappasswordmodify command. In my application I want to be able to set their password without requiring the previous password. I still need the password to obey the history and validation requirements though. I have this working on a similar machine that I set up a while ago and am not sure how I did it.
This is how I am calling the command:
ldappasswordmodify -D cn=mgr -w mgrpw -a uid=user,ou=people,o=systems,dc=program -n newpassword
No matter what password I give it the command works and sets the password.
If I use the command and supply the old password like this:
ldappasswordmodify -D cn=mgr -w mgrpw -a uid=user,ou=people,o=systems,dc=program -c oldpassword -n newpassword
The history and validation requirements are enforced properly.
Does anyone have any idea how to do this or perhaps what to check on the working system to see how I did it before? I'm at a complete loss.
Don't use the manager account. Don't use it for anything actually. Use a user account. The manager account is for slapd itself. It bypasses a lot of security and overlays.
I think this was an issue in OpenDJ 2.4 and it has been resolved in later versions.
You might want to try with OpenDJ 3.0 which is the later release available.
We installed KIE WB 6.1.0 on a Tomcat 7 server on Windows 2012 and created some users. Those users can log in to the Workbench and work on and in the repository.
If I try to clone that repository from another computer, I only get authentication errors:
mb-itmsan01:temp ds$ git clone ssh://admin#192.168.150.34:8001/TestRep
Cloning into 'TestRep'...
Password authentication
Password:
Password authentication
Password:
Password authentication
Password:
admin#192.168.150.34's password:
Permission denied, please try again.
admin#192.168.150.34's password:
Permission denied, please try again.
admin#192.168.150.34's password:
Permission denied (password,keyboard-interactive).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I am sure that the user and password combination is correct ...
Am I missing something, e.g. a role for the user or some configuration? I added all roles which are described in the manual for that user, still no success.
I found out how to fix this problem:
It has been fixed in 6.2.x (currently only available in Beta status). If you want to fix the problem in Drools WB 6.1.x on Tomcat 7, just replace the content in the file WEB-INF/classes/login.config with the following content:
ApplicationRealm {
org.apache.catalina.realm.JAASMemoryLoginModule REQUIRED debug=true;
};
The respective commit on github is:
https://github.com/droolsjbpm/kie-wb-distributions/commit/e53c0c36686822fc17ad5e8aceab39f1de4fb844
After that one can access the Git repository via SSH with the credentials defined in tomcat-users.xml.
I'm trying to setup Hudson to pull from a CVS repo, and need a .cvspass file to do that, and to generate .cvspass, I need to first login manually to CVS (AFAIK).
CVS server in question only seems to support extssh, and I can't figure out how to login into it. I tried something like this:
robert#robert-laptop:~/temp$ cvs -d :extssh:USERNAME:PASSWORD#cvs.server.com:/path/to/project login
cvs login: CVSROOT password specification is only valid for
cvs login: pserver connection method.
cvs [login aborted]: Bad CVSROOT: `:extssh:USERNAME:PASSWORD#cvs.server.com:/path/to/project'.
I tried with and without password, and all other permutations I could think of, but nothing helped. Does someone know a proper way to do it?
UPDATE:
I managed to login and checkout with:
robert#robert-laptop:~/temp$ cvs -d :extssh:USERNAME#cvs.server.com:/path/to/repo co PROJECT_NAME
but .cvspass was not generated, which was the whole point. :(
The error says
cvs login: CVSROOT password specification is only valid for
cvs login: pserver connection method.
Since you do not use a pserver I would try
cvs -d :extssh:USERNAME#cvs.server.com:/path/to/project login
It might be that you can't actually use CVS to store the password. Try to set up a password-less ssh connection. see http://ant.1045680.n5.nabble.com/Authenticating-cvs-extssh-w-o-getting-prompted-td1356537.html
From https://netpenthe.wordpress.com/2007/01/25/extssh-is-an-eclipse-only-cvs-connection-method/
The extssh connection method is unique to Eclipse CVS and doesn’t exist in the
command-line CVS client. If you are using extssh to connect to a SSH2
repository and would like to use the command line client for some CVS
operations you can configure the ext connection method to use extssh when
inside Eclipse.
In other words... checkout the project in eclipse using the ext connection method and not extssh if you want to use the cvs command line client.