S
S.Y.M. Wong-A-Ton
InfoPath forms are saved in XML (=plain text), making the data stored within
them readable/accessible to anyone who can get to the data. You can use a
password within a form to protect it, but if you include the password as a
field in the form, it will be saved along with the other form fields, which
equates to not having applied security at all.
I have written an article on how you can use C# and the .NET class library
to protect InfoPath form fields that contain sensitive information by using a
password and without having to store and/or retrieve this password, making
the forms completely self-contained and providing security through
authentication, privacy, and integrity. This article was published on
ASPAlliance (http://aspalliance.com/784).
them readable/accessible to anyone who can get to the data. You can use a
password within a form to protect it, but if you include the password as a
field in the form, it will be saved along with the other form fields, which
equates to not having applied security at all.
I have written an article on how you can use C# and the .NET class library
to protect InfoPath form fields that contain sensitive information by using a
password and without having to store and/or retrieve this password, making
the forms completely self-contained and providing security through
authentication, privacy, and integrity. This article was published on
ASPAlliance (http://aspalliance.com/784).