Does anyone have any security best practices for building web applications using UniObjects for .NET?
I've placed the connection string in web.config and encrypted it, as well as created a separate remote account with a stripped down VOC. The only data files that can be accessed from this separate remote are the two that the application needs to access (via pointers the main remote account). I also tried to dial down the asp.net trust level runs with, but it seems that uniobjects for .net needs to run with full trust. I guess it's not possible to use connection pooling until UniData 7.1. We are still on UniData 6.1. Is there some other method I could use to limit the number of licenses the web application can grab? Thanks in advance for any pointers. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
