--===============6113305144116650038==
Content-Type: multipart/signed; boundary="nextPart1818306.BMilFMXvQ9"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart1818306.BMilFMXvQ9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

On Thursday, December 18, 2014 02:31:26 PM Martin Klapetek wrote:
> On Thu, Dec 18, 2014 at 1:59 PM, Daniel Vr=E1til <dvratil@redhat.com>=
 wrote:
> > There are usecases when sysadmins want to pre-configure users' Akon=
adi on
> > first login to have their email, corporate calendar etc. configured=
. This
> > would be difficult with KAccounts (IMO). I'm much more in favor of
> > following
> > the current approach of each resource instance having it's own conf=
ig file
> > in
> > ~/.config/akonadi (wouldlaos  make migration much easier for us). J=
ust my
> > $0.02.
>=20
> Technically I think that having pre-configured stuff would be possibl=
e with
> KAccounts,
> the existing accounts are stored in just a sqlite database.

Shipping a pre-configured sqlite database is much harder than shipping =
an INI=20
file.

> Plus I'd assume you'd have to authenticate to that corporate account =
on
> first login anyway?
> What I did in KTp is when it finds a Telepathy account which is not s=
tored
> in KAccounts, it asks for password (which it would anyway because no =
stored
> password exists) and if you choose to save the password, new account =
in
> KAccounts
> is created for that Telepathy account.

Exactly: you ship full config with username and everything (you know us=
ername=20
form LDAP or by current username), the only thing missing is password. =
When=20
you first start KMail, it tries to sync, resource finds it does not hav=
e=20
password and asks for it. You type it in, confirm KWallet and it's done=
.

> However, I believe that the config should indeed be rather stored in =
it's
> own config file.
> The reason is smaller overhead compared to starting and querying KAcc=
ounts.

Also storing full configuration in (binary) database is evil and simply=
 wrong=20
:-)=20

Dan

>=20
> Cheers

=2D-=20
Daniel Vr=E1til | dvratil@redhat.com | dvratil on #kde-devel, #kontact,=
 #akonadi
Software Engineer - KDE Desktop Team, Red Hat Inc.

GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
--nextPart1818306.BMilFMXvQ9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAABAgAGBQJUktj3AAoJEMWdYU9vSuNIyCQH/jjxvEBkavnQ9d6aRKrAAZjG
pyG7fh6EOuxmgvW/NdNGUpPril9bAYq9/98s1LNI4pPOayEq9MyUKMnkNqwvMBHS
YPWf4j1Yojc6vcEwjP2ki5rborNPeO4D0aDEKaNx457Brnh2LiJZlCfi44wekTGp
+B8SF9/v4PwN4oXhe7R5a8uiUM19EQ0PKyzuJfHUO9rEgWkLOVJW5Qm47H7j4FDq
K0A4V1y2U8wInWgFDioWnS3OP764xELdp8VX/PkWVjtS2Xysvg9mqfvf9Ue50Hc1
hzhXKfZEZ4osL9kCYGKvjSquLWQ2zwbcxUlqnKUPbr8y/aZx268wtQ4PNY+JDkU=
=rF/8
-----END PGP SIGNATURE-----

--nextPart1818306.BMilFMXvQ9--


--===============6113305144116650038==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============6113305144116650038==--