zesty-io / manager-ui

Content platform powering enterprise websites and applications
https://www.zesty.io
Other
37 stars 5 forks source link

DUO Mode: Switch on DUO Mode for Existing and New Customers #2399

Open zcolah opened 6 months ago

zcolah commented 6 months ago

Problem Customers do not know about DUO Mode and how to start it. We just want to start it for existing customers and new customers/instance in the future.

Solution Steps Specifically this solution is based around a content policy setting.

agalin920 commented 6 months ago

@zcolah DUO mode is turned on by default if they have it enabled

zcolah commented 6 months ago

@agalin920 this is a ticket that is WIP with Randy. Not yet assigned to any developers therefore.

giseleblair commented 6 months ago

The following settings would be the ideal values to allow to use DUO mode within the product: Settings: Header: X-Frame-Options Content-Security-Policy Referrer-Policy

Screenshot 2023-12-13 at 4 02 35 PM

agalin920 commented 5 months ago

These settings when present disable duomode setting.key === "basic_content_api_key" setting.key === "headless_authorization_key" setting.key === "authorization_key" setting.key === "x_frame_options"

allenpigar commented 4 months ago

@giseleblair @agalin920 i already create a branch (https://github.com/zesty-io/template-pomelo/tree/enable-duo-mode) for this, removing the setting to enable duo mode but the installer template installation does not support deletion of settings. it only updates or creates settings. with this, i think we must also need to delete those settings on the "template base blueprint" since this blueprint creates the base or default setting for the instance before the installer updates or creates the settings for template.

Image

giseleblair commented 4 months ago

I believe that template base blueprint only exists in the database, can you confirm @allenpigar

allenpigar commented 4 months ago

@giseleblair yes it exist on the database and sql scripts are need to update. but as we have discussed, there no need to remove those settings and just set the default value to null. with this, we can just update the values on the template itself without any changes on the blueprint. i already created pr for review.

https://github.com/zesty-io/template-blank/pull/2 https://github.com/zesty-io/template-simple-blog/pull/1 https://github.com/zesty-io/template-pomelo/pull/3