Bug 240413 - accountwizard does not properly detect/set authentication settings
Summary: accountwizard does not properly detect/set authentication settings
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Account Wizard (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Casey Link
URL:
Keywords: akonadi-ports-regression
Depends on:
Blocks:
 
Reported: 2010-06-02 02:18 UTC by Casey Link
Modified: 2017-01-07 21:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Casey Link 2010-06-02 02:18:22 UTC 
Version:           unspecified
OS:                Linux

All the accountwizards for various resources set some hardcoded value for the authentication setting (Clear Text). The script framework is limited in that it only passes back to the scripted setups the encryption (ssl/tls) value.


Reproducible: Didn't try
Comment 1 Thomas McGuire 2010-06-03 19:11:16 UTC 
Assigning to you :)
Comment 2 Casey Link 2010-06-04 23:15:11 UTC 
QtScript's ECMASCRIPT language does not have enum support.

So, fixing this bug in a sustainable way requires the following:

1) string-to-enum and enum-to-string helper functions in an accessible place (transportbase.h)
2) resource agents storing auth types as strings 

It is doable (albeit in an ugly way) with just 1, but that is the minimum.

Both of those options have met with resistance before, so I'll forgo fixing this now. After all the defaults are sane and work in most cases.
Comment 3 Denis Kurz 2016-09-24 20:38:25 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:26:50 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.