New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 653180 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Blocking:
issue 629931



Sign in to add a comment

Open up chrome.logPrivate to apps running in kiosk

Project Member Reported by tbarzic@chromium.org, Oct 5 2016

Issue description

Apps should be able to access their session logs in order to troubleshoot problems encountered when app is running (and include them in their bug/feedback reports). In order to accomplish this, they should be given permission to use an API for retrieving device logs.
Said API already exists (chrome.logPrivate), but is currently available only to set of whitelisted apps - API access should be expanded to apps running in kiosk session.

Few things that should be ensured when opening chrome.logPrivate:
* PII should be scrubbed from retrieved logs
* kiosk app logs should be retrievable by the app
* logs from regular session should preferably not be retrievable by the app

We would probably want to restrict this API to auto-launched kiosk sessions.
 
Cc: sduraisamy@chromium.org

Comment 2 by battre@chromium.org, Oct 19 2016

Components: Privacy

Comment 3 by st...@chromium.org, Mar 3 2017

Cc: r...@chromium.org

Comment 4 by st...@chromium.org, Mar 3 2017

Cc: -st...@chromium.org

Sign in to add a comment