[Cyberduck-trac] [Cyberduck] #10634: No prompt for authorization when connecting to different account
Cyberduck
trac at cyberduck.io
Wed Mar 13 13:06:22 UTC 2019
#10634: No prompt for authorization when connecting to different account
-------------------------+------------------------
Reporter: rth10260 | Owner: dkocher
Type: defect | Status: new
Priority: high | Milestone:
Component: dropbox | Version: 6.9.3
Severity: major | Resolution:
Keywords: | Architecture: Intel
Platform: Windows 8.1 |
-------------------------+------------------------
Changes (by rth10260):
* priority: normal => high
Comment:
Replying to [comment:3 dkocher]:
> I cannot reproduce this issue with two bookmarks for ''Dropbox'' set to
different accounts by distinct username settings.
I can now better document this bug - it's for real!
After your reply I tried one more to make a new connection for account
"B". To my great surprize the operation proceeded right thru the
authorization and completed with seeing the correct Dropbox account.
Using again the New Connection and entering the username to connect to a
different Dropbox account I again get that weird redirection to a wrong
Dropbox account of listed in the booksmarks (and may have been logged in
before in the same Cyberduck session).
It all looks suspiciously like an initialization error, so I exit
Cyberduck and relaunch it.Again I perceive the situation as originally
described. To note once more, connection attempt are thru the New
Connection button, not a bookmark.
A new side effect observed:
I try to make a New Connection to Dropbox using a fake account name
(funny-at-nowhere-dot-net). Not unexpectedly I don't get to see any
Dropbox interaction for verification. BUT to my surprize Cyberduck offers
me an Authorization Code on
https://cyberduck.io/oauth/?state=kUg9Vb8l&code=<some-string>, at the same
time *not* opening the associated dialog to copy the string into it.
Question: is Cyberduck handling invalid account verifications correctly?
I was wondering what may have been the difference from the time original
report and the successful connection following the feedback. Also keeping
in mind as what I perceive to be an initialization error. I then remember
that Windows DLLs can initialize and retain data between invocations. The
Cyberduck installation directory reveals the use of DLLs (no surprize
there of course).
My attempt to prove my case: I create a fresh Dropbox account with another
available valid username / email address. Then I reboot my Notebook. Run
Cyberduck and make a New Connection to this new Dropbox account. Works as
intended!
''Conclusion:'' please check Cyberduck components, especially the Dropbox
connection stuff, for correct handling of reentry / reinvocation and data
retention / initialization.
Regards - Richard
--
Ticket URL: <https://trac.cyberduck.io/ticket/10634#comment:4>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list