Skip to content

GitLab

Last edited by Mark Stevens
Page history
This is an old version of this page. You can view the most recent version or browse the history.

configuration settings and permissions

This would apply for Qbert Configuration Settings and future tablet revisions

Uri Path Read Permission Write Permission Table contents
/handshake normal signature All Values from Configuration soap call not marked as secure
/settings normal normal all values marked as 'public' in Configuration soap call, plus any values stored by an application. basically a free-for-all
/secure signature signature only values marked as 'secure' in Config soap call, plus all values from the provision call
/session normal normal Tablet Session data, free-for-all where data is cleared on session end.

It's possible to apply per-setting permissions, if the exact names are designated as a content uri (eg content://settings/network-timeout ) but the hope is that by isolated content by table we can assert a relative degree of security at a less involved cost.