Custom 401 view is not shown for production hosts.

[dylandepass]

A customer is asking about having this appear on their production host. Is there a reason we excluded it @rofe?

https://github.com/adobe/aem-sidekick/blob/main/src/extension/app/utils/browser.js#L243

[rofe]

@dylandepass I think we don't want customers to use this method of authentication for production (intranet/extranet) use cases or other custom hosts. It was merely meant for to allow authors to connect to preview and live if they are locked down. If customer want to built protected sites in production, they should implement that on their byoCDN using the IDP of their choice.

@davidnuescheler wdyt?

[dylandepass]

Understood. The customer was previously using site authentication in helix 4 (in production) as a way of locking down a site for a intranet use case. So immediately getting kicked to the IDP login worked well for this. The best experience we can offer with helix 5 as you know is for the sidekick to appear and users to login there.

I do agree that this feels outside the intended use case of site authentication.

[rofe]

I don't think we should require site visitors to install the sidekick. They need to implement this differently.