You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a couple of nuances with using the MFA modules on a CWP site.
These should be captured as Developer documentation on the CWP.govt.nz website.
Points to touch on:
Highlight that it will be part of the installer in version CWP 2.6
The TOTP base secret is provided by default on standard CWP stacks, not for the CWP Cloud (AWS) stacks
Docs to ensure that Developers get the TOTP encryption key .env variable for their local dev environment
Point to docs on how to install the modules if not on CWP 2.6
Summary of the feature set, what CMS users it applies to, how to customise the functionality, etc.
Highlight the known limitations and edge cases. This is currently scattered in module documentation and internal support docs. This includes how MFA relates to working with snapshots between environments
Direct readers to more information about the Security Key method, the known limitations, and in what situations it might be a suitable option for sites
One thing to add to the list would be how MFA relates to working with snapshots between environments, e.g. when PROD content is moved to UAT for testing or UAT to local DEV etc.
There are a couple of nuances with using the MFA modules on a CWP site.
These should be captured as Developer documentation on the CWP.govt.nz website.
Points to touch on:
The text was updated successfully, but these errors were encountered: