×
Namespaces

Variants
Actions
(Difference between revisions)

MeeGo 1.2 Harmattan Security Tokens

From Nokia Developer Wiki
Jump to: navigation, search
gnuton (Talk | contribs)
(Gnuton - - APIs that require security tokens)
hamishwillee (Talk | contribs)
m (Hamishwillee - - APIs that require security tokens)
Line 6: Line 6:
  
 
=== APIs that require security tokens ===
 
=== APIs that require security tokens ===
'''UPDATE (12th Dec 2011): Stricken out tokens are not available and methods requiring them to work will be removed from official harmattan documentation soon'''
+
'''UPDATE (12th Dec 2011): Tokens with strikethrough are not available and methods requiring them to work will be removed from official harmattan documentation soon'''
  
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"

Revision as of 21:37, 19 December 2011

Contents

MeeGo 1.2 Harmattan APIs/Qt Quick Modules that require security credentials

This section lists all MeeGo 1.2 Harmattan and Platform APIs and Qt Declarative modules that require security credentials. Please do not add any unnecessary tokens to your application's Aegis Manifest file .


APIs that require security tokens

UPDATE (12th Dec 2011): Tokens with strikethrough are not available and methods requiring them to work will be removed from official harmattan documentation soon

API Required token
Accounts Framework
  • TrackerReadAccess
  • TrackerWriteAccess
Associate Content with Actions
  • TrackerReadAccess
Location Extras
  • GRP::metadata-users
  • Location
  • TrackerReadAccess
  • TrackerWriteAccess
Location Picker
  • Location
  • TrackerReadAccess
QmSystem
  • mce::CallStateControl (check comments below)
  • mce::DeviceModeControl (check comments below)
  • timed::TimeControl (check comments below)
  • dsme::DeviceStateControl (check comments below)
  • mce::LEDControl (check comments below)
  • mce::TKLockControl (https://harmattan-bugs.nokia.com/show_bug.cgi?id=114)
  • mce::DeviceLockControl (check comments below)
QtMobility Contacts
  • GRP::metadata-users
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility Gallery
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility Location
  • Location
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility Messaging
  • Cellular
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility Multimedia
  • GRP::pulse-access
  • GRP::video
QtMobility Organizer
  • GRP::calendar
  • GRP::metadata-users
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility Systeminfo
  • mce::DeviceModeControl (check comments below)
  • mce::TKLockControl (check comments below)
QtSparql RDF Tracker
  • TrackerReadAccess
  • TrackerWriteAccess
Relevance Search
  • relevance::RelevanceAllContentTypes (check comments below)
  • smartsearch::RelevanceAllContentTypes (check comments below)
Share UI Extension API
  • TrackerReadAccess
Single Sign On
  • keychain-access (check comments below)
Web Upload Services
  • TrackerReadAccess
  • TrackerWriteAccess

Description of posix tokens can be found here.

Qt Declarative modules that require security credentials

Qt Declarative module Required token
MapsPlugin
  • Location
QSparql
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility.contacts
  • GRP::metadata-users
  • TrackerReadAccess
  • TrackerWriteAccess

QtMobility.gallery

  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility.location
  • Location
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility.messaging
  • Cellular
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility.organizer
  • GRP::calendar
  • GRP::metadata-users
  • TrackerReadAccess
  • TrackerWriteAccess
QtMobility.systeminfo
  • Cellular
  • mce::DeviceModeControl (check comments below)
  • mce::TKLockControl (check comments below)
QtMultimediaKit
  • GRP::pulse-access
  • GRP::video

(Courtesy of the MeeGo 1.2 Harmattan documentation team)

Almost complete list of tokens available

As Harmattan developer, you have maybe noticed that some applications work correctly only if launched by Qt Creator or via SSH and that they don't work when launched from the phone application menu or by terminal.

In fact, when we run an application as developer or inside develsh, it gets the following security tokens by default: /home/developer $ accli -I Current mode: normal Credentials:

       UID::user
       GID::developer
       CAP::chown
       CAP::dac_read_search
       CAP::fowner
       CAP::fsetid
       CAP::kill
       CAP::linux_immutable
       CAP::net_bind_service
       CAP::net_broadcast
       CAP::net_admin
       CAP::net_raw
       CAP::ipc_lock
       CAP::ipc_owner
       CAP::sys_chroot
       CAP::sys_ptrace
       CAP::sys_pacct
       CAP::sys_boot
       CAP::sys_nice
       CAP::sys_resource
       CAP::sys_time
       CAP::sys_tty_config
       CAP::lease
       CAP::audit_write
       CAP::audit_control
       CAP::setfcap
       GRP::root
       GRP::dialout
       GRP::video
       GRP::pulse-access
       GRP::users
       GRP::metadata-users
       GRP::calendar
       AID::.develsh.
       Cellular
       TrackerReadAccess
       TrackerWriteAccess
       Location
       FacebookSocial
       tracker::tracker-extract-access
       tracker::tracker-miner-fs-access
       libaccounts-noa::accesssvt
       package-manager::packagemanager_limited
       package-manager::packagemanager_private
       icd2::icd2-plugin
       develsh::develsh

But, when the same app is launched by the application menu or by the teminal, it takes only these capabilities. /home/user $ accli -I Current mode: normal Credentials:

       UID::user
       GID::users
       SRC::com.nokia.maemo
       AID::com.nokia.maemo.meegotouchhome-nokia.
       meegotouchhome-nokia::meegotouchhome-nokia

As you can see here, the capabilities granted to applications which run as user are really few. For this reason on harmattan we have Manifest files. A Developer can write only one manifest file for Debian package. Each manifest file can request additional capabilities to one or more applications installed by the package.

What tokens this APIneed?

Here is the list of functions which I don't know what capabilities need to work correctly

  • Bluetooth Mobility API: 'QL2capServer::listen'' fails for low ports. (eg: 0x20). It works fine without requiring tokens for higher ports (eg: 0x1001) or 0x0. It runs fine in develsh without needs of tokens.

Further readings

199 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×