Discussion Locked

Website authentication without cookies

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I work with a team on several website projects that are reference titles aimed at school age kids. Because we sell these sites to schools and libraries we have some authentication we have to go through in order to only allow in users who have purchased access to the sites. Right now we are using cookies to manage this authentication. Once a user is authenticated they can return to the site and the persistent cookie tells the site's server they are allowed in and they don't have to do the username/password thing again.

Our problem is this, many of our users have firewalls at their end that are stripping the cookies out of the headers. This makes our authentication system useless for them unless they punch a whole in their firewall for us to get cookies through. As you can imagine they are reluctant to do this as that is part of why they bought the firewall in the first place. Is there a way I can authenticate users and have them get back into the site during some later sessionwithout cookies?

I'm the most novice member of the team, which is why I'm doing the investigation for alternatives. So blast away if this is an idiotic question!

Thanks in advance,
Doug Farrell

1 reply

by turambar386

Hi Doug. First of all, are you sure that your customers' firewalls are stripping the cookies? I'm sure that there must be some firewalls or proxies that can do that, but I have never heard of them. More likely, these sites have cookies disabled on the browser itself. You may want to take a look at that possibility.

Even if the cookies are being stripped by a gateway, I personally don't believe that cookies are so evil that they need that kind of protection from them. Still, it's not for you to dictate your customers' security procedures, right?

As for alternatives, I can only think of two transparent ways to provide the equvilent authentication:

- digital certificates. Rather difficult to implement and if you maketheir use transparent, you lose most of their strength as an authentication device (because they can be copied onto a floppy disk and used elsewhere).
- only allow access to your restricted web sites from your customers' IP addresses or DNS domainnames. This is *much* easier, and most if not all web servers support these kinds of restrictions.

Hope that helps.

This discussion is closed to new replies.