add possibility to authenticate preview only

[tripodsan]

eg:

• access.allow.live=*
• or access.allow.live=anonymous

this would also allow for different creds:

access.allow.preview=authors.json
access.allow.live=viewers.json

better to reverse structure:

example of preview only auth:

access.preview.allow=authors.json

example of different access groups for preview and live; including api key for live

access.preview.allow=authors.json
access.live.allow=viewers.json
access.live.apiKeyId=xyz

only allow access via api key and authors

access.apiKeyId=xyz
access.live.allow=helix@adobe.com  // required for api key access
access.preview.allow=authors.json
access.preview.allow=helix@adobe.com // users don't inherit from access.allow

workaround

Pre-authenticate requests to .live via an API_KEY on the production CDN

[amol-anand]

I have a customer asking for authentication only for preview and not for live.

[auniverseaway]

+1 to this request. This would be great for us on adobe.com

[davidnuescheler]

@tripodsan i think this is probably not a pipeline only issue or is it? if this has no impact on the delivery stack upstream that would be great.

[tripodsan]

@tripodsan i think this is probably not a pipeline only issue or is it? if this has no impact on the delivery stack upstream that would be great.

@davidnuescheler both. ultimately, the .live requests need to be able to fetch the content unauthenticated. for that several things must happen:

• the edge dicts on .live that mark authenticated sites needs to be removed (admin issue)
• when .live fetches content via .page if needs to be able to do this unauthed. this can be done by not enforcing auth on the live partition. this is a html-pipeline issue

[davidnuescheler]

that's great thanks @tripodsan for the details.

[github-actions]

🎉 This issue has been resolved in version 5.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀