Continuum

svn checkout with authentification doesn't work in 1.2 (trunk rev 663360)

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.2
  • Component/s: Core system, SCM
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

I have a svn repo which needs authentification even for checkout.
In the trunk (rev 663360) with the provided username/password , the checkout failed svn: PROPFIND of '/svn/test/trunk': authorization failed (http://localhost).
To reproduce it you have to cleanup ~/subversion/auth/ .

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Olivier Lamy added a comment -

Well a commit has removed storing scm username/password in the database.
That's why this is broken.
Now we can fix it for the initial checkout : but this will failed if the user choose to not use scm credential cache.
Ideas ?

Show
Olivier Lamy added a comment - Well a commit has removed storing scm username/password in the database. That's why this is broken. Now we can fix it for the initial checkout : but this will failed if the user choose to not use scm credential cache. Ideas ?
Hide
Permalink
Wendy Smoak added a comment -

In the original description, did you check 'Use cached credentials," or not?

Here's what I expect to happen:

With 'use cached credentials' checked, it should use the provided userid/password to get the pom, then rely on cached credentials to do the checkout. It should not store the userid/password in the database.

Without 'use cached credentials' checked, it can store the userid/password in the database and use this later to do the checkout.

Show
Wendy Smoak added a comment - In the original description, did you check 'Use cached credentials," or not? Here's what I expect to happen: With 'use cached credentials' checked, it should use the provided userid/password to get the pom, then rely on cached credentials to do the checkout. It should not store the userid/password in the database. Without 'use cached credentials' checked, it can store the userid/password in the database and use this later to do the checkout.
Hide
Permalink
Olivier Lamy added a comment -

fixed in rev 666882

Show
Olivier Lamy added a comment - fixed in rev 666882
Hide
Permalink
xyz87 added a comment - - edited

Hi

Show
xyz87 added a comment - - edited

Hi

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.