EXT:rsaauth should provide a generic interface
What I think is missing is a more general interface for using the RSA functionality in custom extensions, e.g. login forms and profile edit forms. Only EXT:felogin works out of the box since hooks are provided for that, but I don't see why other extensions shouldn't be able to use RSA authentication/encryption explicitly. It's possible to use the felogin hooks in custom login forms to get identical behaviour, but frontend forms for allowing an user to change his/her password are very difficult to implement (see also https://github.com/pagemachine/hairu/issues/4 and https://forge.typo3.org/issues/25367).
[FEATURE] Add api for rsaauth encryption
This patch introduces new API which eases the use of RSA encryption
across the core and for third party extensions.
For backend encryption a new RequireJS module is included which finds
fields to encrypt automatically by their data attribute.
Reviewed-by: Markus Klein <email@example.com>
Tested-by: Markus Klein <firstname.lastname@example.org>
Reviewed-by: Nicole Cordes <email@example.com>
Tested-by: Nicole Cordes <firstname.lastname@example.org>
Reviewed-by: Georg Ringer <email@example.com>
Tested-by: Georg Ringer <firstname.lastname@example.org>
#1 Updated by Christian Kuhn over 4 years ago
Hey. Your analysis is perfectly right, the current rsaauth architecture misses a generic interface to handle any data, the current hook architecture is doomed. We thought about splitting the extension into two clean parts, but nobody got their fingers dirty, yet.