1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #2655 closed

svn bridge cannot access shared private repositories (BB-1542)

created an issue

So I have an account "runhello". I have a private repository on bitbucket, let's call it SERVERSOFT; there is web software in here that I would like to be able to deploy to a server, so to do this while limiting security risk I created a separate account "mcc_deployer" (I'm assuming that's OK) and granted it readonly access to the repository. I then attempted to check out SERVERSOFT on the server. Here is what I found:

I can successfully:

  • Check out SERVERSOFT, from the mcc_deployer account, using hg.

  • Check out SERVERSOFT, from the runhello account, using svn [and also of course using hg].

  • Check out a public repository created by runhello, anonymously, using svn.

However, if I try to check out SERVERSOFT, from the mcc_deployer account, using svn, this fails. I try:

svn co --username mcc_deployer https://bitbucket.org/runhello/SERVERSOFT/trunk/server

It prompts me for my password several times, then prints:

svn: PROPFIND request failed on '/runhello/SERVERSOFT/trunk/server' svn: PROPFIND of '/runhello/SERVERSOFT/trunk/server': authorization failed (https://bitbucket.org)

Wondering if I'd misunderstood the documentation (http://confluence.atlassian.com/display/BITBUCKET/Accessing+your+Bitbucket+Repository+via+Subversion) I then tried:

svn co --username mcc_deployer https://bitbucket.org/mcc_deployer/SERVERSOFT/trunk/server

Without even asking for a password, it immediately printed:

svn: PROPFIND request failed on '/mcc_deployer' svn: PROPFIND of '/mcc_deployer': 200 OK (https://bitbucket.org)

I realize the svn bridge is beta, however, this seems like some sort of oversight. Thanks!

Comments (5)

  1. runhello reporter

    Hmm, I'm confused. When I reported this bug "SERVERSOFT" was the repository you can now find under runhello/drumcircle and I feel very confident it was not empty at the time I did the above tests. Would you like me to test again?

  2. Log in to comment