Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-8846

SourceTree EE accounts manager unable to reuse stored password

    XMLWordPrintable

Details

    • Bug
    • Resolution: Timed out
    • Medium
    • None
    • 2.5.5
    • UX
    • Severity 2 - Major

    Description

      Hi Atlassian Team,

      As I was writing about our issues with remote tab SRCTREEWIN-8845 where account manager operations were included, I spotted as I was trying to help the remote tab to perform that an credentials prompt was provided to me.

      It should be noted that a part of the fact it didn't popped up and it stood standing ashamed somewhere in the behind of other windows it emerged on very much arbitrary time when I was not concerning this functionality any longer, my impression was it emerged with a very long delay.

      I was very much trying to persuade the account manager to behave in numerous ways....

      First of all it seemed to me that it is starting to do at least something (have some minimal reactions to my actions) where there are more then one accounts defined.

      I was really angry with the behaviour of the (first experience) setup account configuration where there it is a must to click login (pressing enter doesn't do the same thing and) when the credentials prompt (in sourcetree's widget) comes up (the user name is missing there and even if I fill it) after passing it my password as well it replies with "user not found" / "username missing" warning and it fails.
      This behavior is presented when I reach the account manager / credentials prompt by other means as well.

      It also doesn't distinguishes between the same accounts entered with more or less same serverurl ...
      as there are multiple entries of servername:port as well as username@servername:port which refers to a same account.

      There is also an account starting with "Git:" which I assume is the master account I have used when prompted by first experience setup.

      All of the accounts presented in the accounts tab / account manager window are possible to edit / delete or set as default, but none of there options doesn't make sourcetree to reconsider the accounts a part of one of them being changed to default.

      Sourcetree also doesn't care if I let it store the passwords or not, it doesn't use those passwords as it doesn't reload the remote tab when trying to reach the server's repositories (not yet cloned).

      There is a slight chance that switching between accounts and trying to switch to remote tab or refresh its contents with the button that a credentials prompt in window widget will be displayed where there is a chance to issue a password which will be used on next refresh button press. (Y)

      There is also a chance (not being so slight unfortunately) that sourcetree will crash during the accounts mengling which results in some corruption of the profile related files which in turn prohibits sourcetree to start at all.

      It is also possible to achieve the profile corruption by removing the "Git:" tagged account which will again prohibits sourcetree from starting up. (occurred only once)

      There is also second profile files corruption variant when user tries to install and use sourcetree EE on several client machines on the same network.
      After such attempt is made the sourcetree profile is corrupted in the way that the first experience setup will appear everytime sourcetree is run. Second variant of the corruption again prohibits sourcetree from starting at all everagain on the same client machine unless the profile files are completely removed.

      Thank you very much for your support.
      Best Regards,

      Adam Dedek
      Commerzsystems

      Attachments

        Activity

          People

            mminns minnsey
            jirasupport4 AppTech Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: