# Build 882 Mecurial https authentication validation failure

**URL:** https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724
**Category:** Bugs
**Created:** [September 14, 2012, 12:01pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724 "2012-09-14T12:01:59Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Jenasys](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/jenasys/32/888_2.png) [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [September 14, 2012, 12:01pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724/1 "2012-09-14T12:01:59Z")

</div>

G'day,

I was reviewing the progress of the Mecurial HTTP authentication features in this edition and I can see there has been some progress in that area, but I'm still getting failures. It has made me think about the complexities of repository configuration. In my case I use an online service provider (Fogcreek) who have a Kiln authentication plugin to my Mecurial.ini file that handles authentication.&nbsp; If I extrapolate the plugin configuration issues out, I'm not sure how I could configure Continua to handle files that include authentication details for the "runner".

![ContinuaCI_882_Mercurial_validation_failure.jpg](https://www.finalbuilder.com/forums/uploads/default/original/2X/d/d50ff8c4a788495237a5f57da9a54df1d1de5ac2.jpeg)

![ContinuaCI_882_Mercurial-ini_specialisation.jpg](https://www.finalbuilder.com/forums/uploads/default/original/2X/e/e62622bf4a7d9a67e59e4adc26ac56f1a317cad6.jpeg)

---

<div class="post-metadata">

### Author: ![Jenasys](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/jenasys/32/888_2.png) [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [September 14, 2012, 12:04pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724/2 "2012-09-14T12:04:32Z")

</div>

![ContinuaCI_882_Mercurial-kiln-ini.jpg](https://www.finalbuilder.com/forums/uploads/default/original/2X/8/80def0ba39113b5c4660e66b50c2c46538e9e294.jpeg)

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [September 14, 2012, 12:24pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724/3 "2012-09-14T12:24:54Z")

</div>

Hi Jamie   
  
 The issue we are having with https validation is that the only commands that can be run over https are clone/push/pull… status (which is what we use for local and over ssh) results in the error you are seeing. We’re still deciding what to do about this. It’s likely we’ll just handle the ‘not local’ error and treat that as success, since we see a different error with authentication or an invalid repo.

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [September 14, 2012, 12:28pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724/4 "2012-09-14T12:28:45Z")

</div>

We also need to do some more testing with Kiln. We use mercurial internally as the source code transport between the server and the agents… for non mercurial repos we wrapper them with hg, but for hg repos we just use them as is. My concern with kiln is that their extensions may break our transport. We’ve been testing ssl support using bitbucket so I know that plain hg over ssl does work.

---

<div class="post-metadata">

### Author: ![Jenasys](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/jenasys/32/888_2.png) [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [September 14, 2012, 12:41pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724/5 "2012-09-14T12:41:42Z")

</div>

I’ll admit that the current https://{username}:{password}@{hg url} solution in Continua is of a worry with a password in the URL. I understand Kiln are working on SSH support, which might negate this discussion in the long run. That feature isn’t complete at the moment, but has been on their radar for some time.   
  
 [http://kiln.stackexchange.com/questions/824/anyone-manage-their-continuous-integration-with-teamcity-finalbuilder-and-mercu/826#826](http://kiln.stackexchange.com/questions/824/anyone-manage-their-continuous-integration-with-teamcity-finalbuilder-and-mercu/826#826)

---

<div class="post-metadata">

### Author: ![Jenasys](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/jenasys/32/888_2.png) [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [September 14, 2012, 12:43pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724/6 "2012-09-14T12:43:59Z")

</div>

I’ve also had a look at the access tokens for Kiln to see if that would resolve the issue for CI servers. [http://kiln.stackexchange.com/questions/4054/what-are-access-tokens-do-they-let-me-avoid-using-up-a-license-on-my-continuous](http://kiln.stackexchange.com/questions/4054/what-are-access-tokens-do-they-let-me-avoid-using-up-a-license-on-my-continuous). It didn’t.

---

<div class="post-metadata">

### Author: ![Jenasys](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/jenasys/32/888_2.png) [@Jenasys](https://www.finalbuilder.com/forums/u/Jenasys)
#### Post date: [September 14, 2012, 12:47pm UTC](https://www.finalbuilder.com/forums/t/build-882-mecurial-https-authentication-validation-failure/5724/7 "2012-09-14T12:47:26Z")

</div>

Kiln v3.x will support SSH, due before the end of this year.

http://kiln.stackexchange.com/questions/3641/feature-request-ssh-support![](upload://22zzdImDEY8lkuJinMzoyyHWell.jpeg)

&nbsp;

![Continua\_Kiln\_SSH.jpg|500x250](upload://22zzdImDEY8lkuJinMzoyyHWell.jpeg.jpeg.jpeg.jpeg)
