Hello guys i made a workspace and i dont know when it asked for encrption password. I forgot the password and now my developer cannot pull code, he is always prompted for encryption password.
So what is the solution, should i make a new workspace or make a new Plastic SCM account and then a new workspace.
The encryption configuration is stored in the following paths: You can share the files with your coworker:
Server-side encryption configuration:
C:\Program Files\PlasticSCM5\server\cryptedservers.conf
C:\Program Files\PlasticSCM5\server*.key
Client-side encryption configuration:
C:\Users\xxx\AppData\Local\plastic4\cryptedservers.conf
C:\Users\xxx\AppData\Local\plastic4*.key
Related
I want to import TFS repo to git and clone into my local machine and I am using git-tf. Below my code:- git-tf clone http://server:8080/tfs/DefaultCollection $/SampleProject D:\TFSRepoName I want to pass username and password in url , so it automatic clone repo without asking for username and password.
If you don't want to be prompted for credentials every time you run git-tf, you can store your credentials in your GIT configuration for your repository:
$ git config --global git-tf.server.username your-username
$ git config --global git-tf.server.password your-password
Note that your password will be stored in the git configuration file in plain text. Be sure to set the ACLs or file permissions as appropriate to discourage people from reading your password out of your configuration file. Or you can store just the username and you will need to type only your password each time.
Reference : Accessing TFS with git-tf
You can also try to install and Use the Git Credential Manager,
When you connect to a Git repository from your Git client for the
first time, the credential manager will prompt for your credentials.
Once authenticated, the credential manager will create and cache a
personal access token for future connections to the repo. Git
commands that connect to this account will not prompt for user
credentials until the token expires or is revoked through VSTS/TFS.
One way to pass the credential is -
git pull http://username:password#url
Here "url" will be the url you use to clone the repository on tfs.
But this way is not recommended. Instead you should go for credential manager.
I had to use the default windows credential manager (windows 10 comes with this feature).
Control Panel\User Accounts\Credential Manager
Click windows credentials
Add generic credential
git:(tfs url, no trailing slash) ... example: git:http://tfs
username .. example: domain\username
password
save
Next time you use git for this url your saved credentials will be used
Trying to push Xcode project to TFS (Git repository), i created local repository for my project in Xcode, then install Git Credential Manager from GitHub, then trying to connect repository from Xcode by adding remote or connect to git repository, but the error message is "Authentication failed because the authentication credentials were rejected."
Would you please provide me with the correct steps.
Knowing that TFS 2015 & Xcode 8.2
The easiest solution for me was to just add your local repository with command line.
git remote add origin ADRESSOFREPO
Afterwards you can use the version control in Xcode to push and pull
TFS 2017 offers you SSH access. The earlier versions, like 2015, requires to setup SSL and Basic Authentication on the server. I guess that this is not properly configured for you.
The steps to setup SSL are described in details in the docs.
Here you can find what is required to configure Basic Authentication.
A couple of caveats:
username should be entered in domain\user format
do not enable Basic Authentication on the default non-SSL site
Has anyone successfully set up VSO & Jenkins & TFS?
Server URL: https://<myproject>.visualstudio.com/DefaultCollection
Login name and user password (using alternative credentials)
What domain name did you use? <domain>\username
If I run the tf command in Command Prompt, it succeeds, but Jenkins shows the same command as failing. I'm lost as to how to debug this. I also tried setting cached credentials for TFS, and not caching them. It seems as though Jenkins does not have cached credentials, but my command prompt does? Why would my system have stored credentials for me, but not Jenkins?
Error from Jenkins: TF30063: You are not authorized to access https://windwardstudios.visualstudio.com/DefaultCollection
With the release of version 4.0.0 of the Jenkins Team Foundation Server plugin, Team Foundation Version Control (TFVC) from Visual Studio Online (VSO) is now officially supported and both Personal Access Tokens (PAT) & alternate credentials can be used.
See the section User name and password in the wiki page.
This is an answer, but may not be what you want to hear. This used to work for us about a year ago. It required someone to stay logged into VisualStudio.com with his MSDN credentials on the build server. Then we simply didn't use credentials in the Jenkins TFS plug-in. Then one day, that simply stopped working. We tried alternative credentials, as #MrHinsh suggested, but never got it to work. Eventually we gave up and switched all of our TFS repositories to git (but still hosted on VisualStudio.com). That does work with the alternate credentials, and we have been very pleased since.
You need to configure Jenkins yo use the alternate credentials. It will not work with any other configuration and the credentials are never stored. Every command that you pass must include the same creds.
I'm trying to connect to a repository tfs a written project with xcode 5.
I'm using git-tf and it seems that the configuration in xcode 5 is correct.
The problem that feedback occurs when authentication with the TFS repository.
In xcode 5 open preferences and go in the accounts. I enter the login information with the url and in response I Access denied credentials are incorrect.
What am I doing wrong?
I was encountering the same issues when trying to authenticate in Xcode 5.
Make sure that you enabled Basic Authentication for your user profile for the TFS user account and that you selected "New Team project + GIT" instead of "New Team Project".
You can also try to clone the repository by using Terminal. Type the following command into Terminal and replace XXXXX with your values.
git clone https://XXXXX.visualstudio.com/DefaultCollection/_git/XXXXX
Then provide your credentials. Terminal will now clone the repository when authentication succeeds and your credentials will be saved to your keychain. Now when you try to authenticate in Xcode it will use the saved keychain credentials and it will (probably) successfully add your TFS repository to Xcode.
I hope this will help you!
See:
http://tfs.visualstudio.com/en-us/learn/use-git-and-xcode-with-tfs.aspx
for more information
https://www.visualstudio.com/en-us/get-started/share-your-xcode-projects-vs
Share your Xcode projects in Visual Studio Online using a Git repository. Or, if your team project uses TFVC instead of Git, you can use the git-tf command line tool to check your files into Visual Studio Online.
Enable alternate credentials
You can’t sign in to Xcode with an account that contains an # character, so you’ll have to enable alternate credentials.
I made a new blank TFS git project and tried to clone it in a new folder on my desktop using TortoiseGit and msysgit. It always fails saying 'Authentication failed'.
I typed:
"git clone https://saratoga.visualstudio.com/DefaultCollection/_git/Git%20Test."
When prompted for my username I entered my Windows account email address (e.g. bob#example.org).
It then asked for my password for
"https://test#saratoga.visualstudio.com"
i entered the password. However, I am unable to connect to the tfs service, message appear that authentication failed in tortoise git.
Alternative Authentication Credentials in TFS provides a solution, use the following instructions:
Click on your name in the upper right of screen.
Click on My Profile.
Click on the Credentials tab.
Setup an alternate username that doesn't include the # character.
Now when you connect to the remote repo via TortoiseGit, you can use the alternate credentials and those new credentials should work.