You could use a service on another server inside your firewall that does all of the universe access. Then your web app would only be able to communicate with that service.
Thanks, Nick Cipollina -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Kubarych Sent: Tuesday, July 10, 2007 2:54 PM To: [email protected] Subject: [U2] UniObjects .NET - Security Best Practices, Connection Pooling in UD 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 [email protected] To unsubscribe please visit http://listserver.u2ug.org/ CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
