The information on this page is intended for network administrators and addresses issues that may be encountered by users using AESDirect to file SEDs over the Internet. This page will be updated in the future with additional information as neccessary.

Encryption

Because AESDirect involves the transmission of confidential information it requires the use of 128-bit encryption. We have implemented this using a Global Server ID from Verisign which enables 128-bit RC4 encryption in all domestic and export versions of Netscape Navigator/Communicator 4.0 and higher and Microsoft Internet Explorer 4.0 and higher. If your employees connect to the Internet through a firewall or proxy server, you will need to make sure that they are capable of making secure sockets layer (SSL) https connections to our server. Since https connection use TCP port 443 on the server side you will need to either allow connections to this port through your firewall or proxy server.

Any portions of the site that require a user to send their username and password are encrypted. This includes the application itself, the tutorial and quiz, and the e-mail form to send a question in the support center. Usernames and passwords are never sent in clear text.

If your users report any http 403.5 errors or an being able to connect to unencrypted portions of the site but not to the encrypted portions (listed above), this is likely due to an inability to make a the https connection. You should check to make sure that SSL v3.0 encryption with 128 RC4 encryption is enabled in their browser (it is by default), and that the connections are being allowed through your firewall/proxy server correctly.

Cookies

AESDirect uses transient (not stored) cookies. Please make sure that users have cookies enabled in their browsers and that if you have a proxy server it is passing the cookies to and from our server.