6.1 Do you support SSL?

Yes. SSL was implemented in the AvantGo Client version 3.3. All current users of the AvantGo Client can connect securely to websites. See APPENDIX E. Security.

6.2 Really? How does that work?

For more details, see the Secure Connections section of our User's guide FAQ.

6.3 You say that the AvantGo Client uses a Certicom Elliptical Encryption Algorithm. I do not think my web server supports that.

No problem — that is just on the device itself. When our sync servers talk to your web servers, we use the normal RSA encryption that your server has been dealing with for years.

6.4 What do I do if I want pages on AvantGo channel to be secure?

You would create them the same way you would on your website. Keep in mind, however, that not all users will be able to view this secure page. Only users who have version 3.3 of the AvantGo Client, and have manually turned on Connect Securely in their server preferences will be able to view this secure page.

6.5 How can I tell if a user is or is not connecting securely?

You can look at their HTTP headers for the presence or lack of an X-AvantGo-SecureSync header. See Using AvantGo Client HTTP request headers to customize content for more information on how to do this.

6.6 I am creating a channel and I want to restrict it to only certain users. How can I do this?

Generally, I recommend doing this with cookies. Create a login page where, if your user has successfully logged in, you store their login name and/or other pertinent information in a cookie. See Using cookies to support personal channels.

We also support HTTP authentication on the device, although the user experience is just mediocre. Once your user enters their name and password, they just get a blank page until they sync again.