The API should accept provider IDs as service IDs

Bug #1488429 reported by Alberto Mardegan
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Online Accounts API
Alberto Mardegan

Bug Description

The OA manifest file allows apps to specify services like this:

  services: [
    "provider": "facebook",

but currently the QML and Qt APIs (for example the requestAccess() method) expect a service ID, which would be in the form "myapp.developer_myapp_facebook", which is not very intuitive since these long IDs are not used in the manifest file.

Given that the API doesn't allow an application to use more than one service per provider anyway, we should accept provider IDs as parameters in the API, and just build the full service ID ourselves.

Revision history for this message
Alberto Mardegan (mardy) wrote :

Actually, I'm not sure about this. The service IDs are also returned by the AccountModel in the "serviceId" role and as the "serviceId" property of the Account objects. It would be weird to have these IDs coming from the API being different from those passed to the API.

Changed in online-accounts-api:
importance: Critical → Low
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.