1. Jens Alfke
  2. Murky
Issue #17 open

Support for http authentication

Benjamin Bock
created an issue

When trying to pull from a http auth protected repository I get: {{{ hg command error: abort: http authorization required }}}

Would be great if Murky would ask me for username/password (maybe with the option to store it or save it for the session, ...)

Comments (26)

  1. Benjamin Bock reporter

    An addition: When providing the username:password in the URL, the password is shown in the pull-window. It would be better if it was hidden as it is in the output:

    pulling from http://beb:***@code.example.org/myrepo
    searching for changes
    adding changesets
    adding manifests
    adding file changes
    added 449 changesets with 3008 changes to 1378 files
    1230 files updated, 0 files merged, 130 files removed, 0 files unresolved
    
  2. Olivier Scherler

    Today I tried to push to my BitBucket fork, that I had cloned via HTTP, so the push sheet got stuck on "password:" as if it was interactively asking for the password. Maybe the --noninteractive option is missing.

  3. David Keegan

    Right now this is my # 1 request for Murky. I added the launch terminal button to get around this issue, but its annoying to have to jump to terminal to push an authenticated repository.

    What do you think is the best solution? Keychain?

  4. Anonymous

    I like to see it too .... A Keychain intergration is on Mac almost mandatory...

    How is the status?

  5. Barry Earsman

    The easy workaround for this issue is to add your authentication details as an "auth" section into the .hg/hgrc file, off the root of your local repository, eg:

    [paths]
    default = https://hg.myserver.com/myproject
    
    [auth]
    myserver.prefix=hg.myserver.com/
    myserver.username=myusername
    myserver.password=mypassword
    myserver.schemes=https http
    

    More info here: http://www.selenic.com/mercurial/hgrc.5.html#auth

  6. Log in to comment