Has anyone successfully been able to obscure url parameters when using prefill? For example if I want to pass the email field via the url to a FormAssembly form to use to prefill other fields on the form what would be the best way to do this.
Agreed, you do not want to pre-fill based on email alone -- then I could try email addresses of people I think are in your database and pull out the rest of their information that you are prefilling. As @Josue Ramirez Bonilla noted I recently wrote a blog post where I strongly
discourage using the Salesforce ID since they can be iterated over in a similar manner.
In short whatever you put in the URL needs to be something a bad actor cannot guess and/or try A LOT of? So Email addresses they can guess a bunch. Ids they can test a large number in sequence. It
mightbe okay to use email AND SFID depending on the level or risk you are willing to accept (this would likely hold off most bad actors in practice, but has theoretical weaknesses so if you data is high value I wouldn't use it).
You have a few options depending on your details:
- Generate a UUID for each person you are contacting, and have that trigger the prefill. This is the idea I discuss some in the blog post, and it includes some references to code that can help.
- Since you're on FormAssembly you can use their secure parameters pattern: https://help.formassembly.com/help/508885-prefill-lookups-using-secure-parameters
- Use SSO authentication from another system the users would be logged into anyway to limit who can reach the forms and what FormAssembly knows about them.
