Comments on: InfoPath Demo: Password-protect InfoPath forms in SharePoint

By: S.Y.M. Wong-A-Ton

S.Y.M. Wong-A-Ton — Mon, 22 Mar 2010 00:48:41 +0000

Come to think of it, you should not have issues with the InfoPath controls themselves, because the protectedData field is a hidden field (not shown on any View).

I don’t know whether the “base64Binary” data type accommodates more characters than the “string” data type, but you should be able to find out. Since you’ll be writing to XML nodes through code, it should not matter what you use in the data source.

Another thing that could fail when you use a large amount of text are the .NET methods to encrypt and decrypt. Again, if you hit any limitations, you may have to come up with a way to split the fields into multiple group nodes or be very selective as to which fields need protection and which do not.

Let me know how you get on.

By: S.Y.M. Wong-A-Ton

S.Y.M. Wong-A-Ton — Sun, 21 Mar 2010 23:44:27 +0000

Those are all valid questions, which to be honest I have not tried out. Worst case scenario, you’d have to split the protectedData field up into multiple fields to accommodate your 39 fields.

I don’t know what the limitations are of controls in InfoPath, so you’d have to give it a try. If it does not work, let me know. And if you find something worth mentioning, let me know too.

By: StefanS

StefanS — Sun, 21 Mar 2010 10:57:21 +0000

Luctor et Emergo

Thanks for the solution.

Since the encryption blows up the amount of characters of the protectedFields nodes, will it become a problem to store my 39 fields in the encypteddataField that is of the type string with a certain limit on number of characters. Is the base64 attachment field maybe more usefull here and easy to apply since we are already using System.Security.Cryptography ?