Open markstuart opened 1 year ago
Well, it actually is mentioned in the README, although it's not specifically stated to be an advantage over core: "no modifications to existing forms". The core protection has to be disabled if you're using a plugin that hasn't been updated to work with it. This doesn't; it will inject tokens to any template on the fly.
Hi team, just wondering if it'd be worth adding some information in the README to indicate why someone might choose to use this extension over the CSRF protection that CKAN core now provides?
Clearly this extension is great for anyone on older versions of CKAN, and we recommend it alongside the https://github.com/data-govt-nz/ckanext-security extension, but possibly it also provides more extensive CSRF protection than the core implementation?
@ThrawnCA any ideas on this?