PoisonArrowFrog Posted March 7, 2014 Report Share Posted March 7, 2014 Hi, We have a git repository that is hosted on OSX 10.9 (Server) Xcode git server. We have created a empty plastic repository with the hopes of syncing our git repository to plastic. Unfortunately after specifying our git server's https (and http) address and a username and password in the GitSync dialog we consistently get the error "the credentials introduced for the repository are not valid". We can access the repository fine through SourceTree. Also we have successfully synced a Bitbucket repository to Plastic but as I understand we should be able to sync from our own server. Any ideas? Thanks, Mike Link to comment Share on other sites More sharing options...
calbzam Posted March 14, 2014 Report Share Posted March 14, 2014 Hi, Is it possible for us to test the Sync operation? Could you try using command line? Usage: cm sync spec git [--user=username] [--pwd=password] spec: Full repository specification. url: Remote repository url, including http(s):// or git://. Options: --user: User name for the specified url. --pwd: Password for the specified url. Regards, Carlos Link to comment Share on other sites More sharing options...
PoisonArrowFrog Posted March 17, 2014 Author Report Share Posted March 17, 2014 OK I tried your suggestion and get the same results. Your prompt reply with any suggestions is appreciated. Thanks, Mike mother:sfp_plastic admin$ cm sync sfp@mother.bj.private:8087 git https://mother.bj.private/git/sfp.git --user=blah --pwd=foo ERROR building certificate chain: System.ArgumentException: certificate ---> System.Security.Cryptography.CryptographicException: Unsupported hash algorithm: 1.2.840.113549.1.1.11 at Mono.Security.X509.X509Certificate.VerifySignature (System.Security.Cryptography.RSA rsa) [0x00000] in <filename unknown>:0 at Mono.Security.X509.X509Certificate.VerifySignature (System.Security.Cryptography.AsymmetricAlgorithm aa) [0x00000] in <filename unknown>:0 at System.Security.Cryptography.X509Certificates.X509Chain.IsSignedWith (System.Security.Cryptography.X509Certificates.X509Certificate2 signed, System.Security.Cryptography.AsymmetricAlgorithm pubkey) [0x00000] in <filename unknown>:0 at System.Security.Cryptography.X509Certificates.X509Chain.Process (Int32 n) [0x00000] in <filename unknown>:0 at System.Security.Cryptography.X509Certificates.X509Chain.ValidateChain (X509ChainStatusFlags flag) [0x00000] in <filename unknown>:0 at System.Security.Cryptography.X509Certificates.X509Chain.Build (System.Security.Cryptography.X509Certificates.X509Certificate2 certificate) [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at System.Security.Cryptography.X509Certificates.X509Chain.Build (System.Security.Cryptography.X509Certificates.X509Certificate2 certificate) [0x00000] in <filename unknown>:0 at System.Net.ServicePointManager+ChainValidationHelper.ValidateChain (Mono.Security.X509.X509CertificateCollection certs) [0x00000] in <filename unknown>:0 Please, report this problem to the Mono team Receiving references... /Error: The credentials introduced for the repository are not valid Link to comment Share on other sites More sharing options...
anuar Posted March 18, 2014 Report Share Posted March 18, 2014 Hello Mike, Thanks for the report. This seems to be a bug in version of Mono distributed with Plastic SCM. The good news is that this bug is fixed in the latest version of Mono. You can try to get it working by installing the latest version of Mono from http://www.go-mono.com/mono-downloads/download.html (currently 3.2.7) and running the sync command using the new mono: $ mono /Applications/PlasticSCM/Client/cm.exe sync sfp@mother.bj.private:8087 git https://mother.bj.private/git/sfp.git --user=blah --pwd=foo Please, let us know if this worked for you. Regards, Anuar Link to comment Share on other sites More sharing options...
PoisonArrowFrog Posted March 24, 2014 Author Report Share Posted March 24, 2014 I'm a bit hesitant to install the new Mono version given that it's unclear how it might break other things. I would expect that the Plastic distribution would contain the release that works the best. At any rate I installed a plastic client on windows and preformed the sync with the command line and received: "Error: The credentials introduced for the repository are not valid" The issue doesn't appear to be related to Mono. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.