Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N notebook
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mark Stevens
  • notebook
  • Wiki
  • configuration settings and permissions

Last edited by Mark Stevens Apr 14, 2017
Page 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 signature signature All Values from Configuration soap call not marked as secure
/settings normal signature all values marked as 'public' in Configuration soap call, plus any values stored by an application. Shareable to 3rdParties, but curated by us
/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, basically a free-for-all for sharing name/value pairs among apks 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.

Clone repository
  • branch code plan
  • build and test configuration
  • build artifact versioning
  • build server instrumented testing
  • build server move
  • bzt16wifi02 releases
  • bzt18uxa02 releases
  • configuration settings and permissions
  • create a repo from cli in gitlab
  • engineering status
  • feature deployment
  • gitlab installation instructions
  • Home
  • ota update and deployment
  • qbert implementation
View All Pages