Comment 12 for bug 1643732

Thanks for taking the time to explain the idea. :-)

I have to tell you, that the new online-accounts-api is simpler than the
other API we have, and it's so in virtue of its more limited scope: it
was initially designed for click applications, or for unconfined
services acting on behalf of a specific click application.

I'm quite confident that we can make it work for your use-case, but some
compromises might be needed.

The more you explain the goal, the more I get convinced that the storage
framework needs to be registered as an app with Online Accounts. Once we
can properly identify the storage-framework as the initiator, we can
then make some tweaks on the UI on our side, if there is the need to;
for example, if we need to customize the access request screen we show
to the user when creating/authorising a new account (which, currently
shows icon and name of the requesting app, which might not be what we
want in this case).

In order to do the above, you need to ship the .application file I've
mentioned before. The fact that the API works without specifying a valid
applicationId is not intentional, and is in fact a bug.

Please see
https://bugs.launchpad.net/ubuntu/+source/online-accounts-api/+bug/1638769/comments/7
and let me know if you think there's something wrong in all this. :-)