filemaker soap using baseelements plugin

#Filemaker soap using baseelements plugin pro

Encrypting at the field level prevents unauthorized users from accessing sensitive data in open FileMaker files, whether that be from exporting records, checking out a field value in Data Viewer, or accidentally stumbling upon a developer layout displaying the field.

#Filemaker soap using baseelements plugin pro

Encrypting the entire database at rest, using FileMaker Pro 13 Advanced's new file-level encryption, is also important in protecting sensitive data, but will not help you once a user has the database open. The new encryption functionality in the BaseElements plugin allows you to securely store sensitive data, such as credit card numbers and SSNs (ideally you wouldn't store this data, but if need be, encryption is an important component of PCI and HIPAA compliance). The latest beta version of the BaseElements plugin (2.3 as of ) now includes a set of AES encryption functions that can be used to encrypt text fields in a FileMaker database.

So, as history tends to do, we repeated ourselves by sponsoring the development of the plugin again, but this time for encryption functions. Just as we've needed HTTP POST many times over the years, we've also needed field-level encryption. Since then, we've used the HTTP POST functions in many web service integrations and are thankful for Goya's continued contributions to the FileMaker community with this Swiss-army-knife-esque, open-source plugin. In fact we love it so much we decided to sponsor the development of HTTP POST in the plugin back at the beginning of 2012. We here at DB Services love the BaseElements plugin.