New issue
Advanced search Search tips

Issue 835965 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

[FR] Support CWS Private App Publishing with visibility limited to domain enrolled devices

Project Member Reported by c...@chromium.org, Apr 23 2018

Issue description

Description:
In the CWS (Chrome Web Store) customers want to publish private apps which can only be accessed by enterprise domain enrolled Chrome OS devices.  This includes support for setting the visibility of published Chrome Apps & Extensions to Private.  Private in this case means that only users/devices limited to the domain enrolled.

Use case:
Provide granular Chrome Web Store app publishing controls to further limit/restrict who has access to Chrome Apps & Extensions.  

Motivation:
Customers want to publish Chrome Apps and Extensions where no public access is allowed.  Unlisted is NOT a good enough option as anyone with the full URL to the app can still potentially install the app/extension.

Existing workarounds:
Set visibility option in the CWS to UNLISTED.  Not a secure method, still visible to those who have access to the encrypted URL.  One other issue is that single-app mode only works when CWS app is published as PUBLIC or UNLISTED.
 
Cc: jawag@chromium.org
Owner: privard@chromium.org
Assigning to Chrome and CWS folks. 

Comment 2 by jawag@chromium.org, Apr 25 2018

Labels: Needs-Feedback
Hello, this functionality already exists. Here's some help content on how organizations can publish apps & extensions with restricted access: https://support.google.com/chrome/a/answer/2663860?hl=en

Is that what you're after?

Comment 3 by c...@chromium.org, Apr 25 2018

Customers require app publishing to be private but also accessible from kiosk/single-app modes (non-user modes).

Currently the only supported CWS visibility methods are (1) Public and (2) Unlisted.  Public is NOT an option.  Unlisted is deemed still insecure as one could potentially access CWS App if the URL is obtained.  
Cc: -jawag@chromium.org privard@chromium.org
Labels: -Needs-Feedback
Owner: jawag@chromium.org
This is really a question for the CWS team. Reassigning to jawag@.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".

Sign in to add a comment