[CUG] Pages and folders with restricted access

[rofe]

Overview

So far, Helix assumes all content to be publicly available. Now for certain content, authors should be able to protect it with a username and password.

Details

This came up as a fringe use case on blog project: PR people want to share assets with press - videos, images, bios, etc - and don't like using dropbox but rather a way to to set up the assets in an easier way for the press to grab assets and also get the story.

Proposed Actions

Let's discuss how in our current architecture we could allow flagging certain documents (or paths) as requiring authentication, and how an author could specify a dedicated username and password for their content. It could also be a Helix Pages only feature, at least in the beginning.

[rofe]

In Word (desktop version only), you can protect a document by specifying a password for read and/or read/write. Maybe we could somehow leverage that in word2md. The disadvantage would be that such documents could no longer be viewed/edited online.

[avanishgandhi]

should we look to use Brand Portal or asset share features from AEM. Blogs platform is not the right place to manage such assets. I will setup a call to discuss with Matt R.

[rofe]

@avanishgandhi as far as the blog project is concerned, let's create a separate issue in the project repo. This issue meant to be a more generic discussion about how to implement such a use case in Helix going forward.

[davidnuescheler]

i think that for the use case of the blog, i think a url that's hard to guess should be just fine.