Bug 424553 - Authenticating to flickr does not work
Summary: Authenticating to flickr does not work
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-Flickr (other bugs)
Version First Reported In: 6.4.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-23 00:49 UTC by Rob Brown
Modified: 2020-07-23 05:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 7.1.0
Sentry Crash Report:

Attachments
screenshot of error (40.82 KB, image/png)
2020-07-23 00:49 UTC, Rob Brown 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Brown 2020-07-23 00:49:15 UTC 
Created attachment 130326 [details]
screenshot of error

SUMMARY
Authenticating to flickr fails for digikam

STEPS TO REPRODUCE
1. Export menu >> Export to Flickr
2. Add another account
3. Flickr Launches, I click 'ok I'll authorize'
4. flickr fails

OBSERVED RESULT
I get following error message:

Secure Connection Failed

An error occurred during a connection to 127.0.0.1:1965. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.


EXPECTED RESULT
After authorizing, I should be sent back to digikam and account is added.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-26-generic
OS Type: 64-bit
Processors: 16 × Intel® Xeon® CPU E5520 @ 2.27GHz
Memory: 11.7 GiB of RAM

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2020-07-23 02:15:16 UTC 
Please try with 7.0.0:

https://download.kde.org/stable/digikam/7.0.0/

Gilles Caulier
Comment 2 Maik Qualmann 2020-07-23 05:31:55 UTC 
Yes, the return callback address that is no longer valid is fixed in digiKam-7.0.0 with this commit:

https://invent.kde.org/graphics/digikam/-/commit/16b1ad17d632ef5638979b43cd657f911e9e71cf

Maik