Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M mercurial_keyring
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • mercurial_keyring
  • Issues
  • #13

Closed
Open
Created Nov 29, 2011 by Bitbucket Importer@bitbucket_importerOwner

Push requires manual password entry even when auth data is stored

Created originally on Bitbucket by Levi Bard

It appears that mercurial_keyring is falsely detecting an authorization failure, then invalidating stored auth data. Using Mercurial 2.0, the issue appears to manifest identically on Linux (Ubuntu 11.10), Windows (7 x86-64), and OSX (10.7).

{{{ $ hg --debug push pushing to http://rhodecode/mybranch using http://rhodecode/mybranch sending capabilities command [HgKeyring] Keyring URL: http://rhodecode [HgKeyring] Username found in .hg/hgrc: levi [HgKeyring] Looking for password for user levi and url http://rhodecode [HgKeyring] Keyring password found. Url: http://rhodecode/mybranch, user: levi, passwd: ********* query 1; heads sending batch command [HgKeyring] Keyring URL: http://rhodecode [HgKeyring] Cached auth data found. Url: http://rhodecode/mybranch, user: levi, passwd: ********* searching for changes all remote heads known locally query 1; heads sending batch command [HgKeyring] Working after bad authentication, cached passwords not used {'realm': 'RhodeCode authentication', 'user': 'levi', 'authuri': 'http://rhodecode/mybranch?cmd=batch'} [HgKeyring] Keyring URL: http://rhodecode [HgKeyring] Username found in .hg/hgrc: levi http authorization required realm: RhodeCode authentication user: levi (fixed in .hg/hgrc) password: }}}

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking