On Fri, 2010-10-08 at 21:22 +0100, Alberto Mardegan wrote:
> 
> > Is there some example code, or can you point out the relevant
> methods?
> 
> To create an account, it's as simple as calling:
> 
> // "MyProvider" doesn't need to exist for this to work
> Accounts::Account *account = manager->createAccount("MyProvider");
> account->setEnabled(true);
> account->sync();
> 
> Then you can open ~/.accounts/accounts.db with a SQLite client.

I tried that after setting up a mail account with the qtmail app on
MeeGo Trunk (Qt frontend for MeeGo's QMF, which should use Accounts&SSO
under the hood).

It seems that the version in MeeGo Trunk (1.0.7~2010w36-1.4) doesn't use
SSO. I found that my username/password are attached to the Account,
without any Identity involved:

INSERT INTO "Settings" VALUES(3,1,'imap4/username','s','google-user');
...
INSERT INTO "Settings" VALUES(3,1,'imap4/password','s','Z29vZ2xlLXBhc3N3b3Jk');

Either that version is too old, or the code about SignOn::Identity in
the latest QMF source isn't doing anything.

Vitaly, how do MeeGo version numbers of QMF match with the tags in git?
Does the source file qmf-1.0.7~2010w36.tar.gz match with tag 2010W36?
The code for SSO was included in the tag following 2010W36_3, so it
seems that we don't have it in MeeGo yet. If we did, would QMF only
*use* an existing Identity attached to an account or would it also
*create* an Identity to store credentials passed in from apps? I get the
feeling that it is the former.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to