I'm sorry if I wasn't clear. My problem is that some of the public users may not have email addresses (That's a reality in many developing countries.) but I still need to try to minimize duplicate registration (i.e. same name, gender, dob, etc. cannot register again so i need to authenticate against a db.)
The 'public' users are not random visitors. They need to the interact with the institution via the portal. It could be a one-time visit (prevalent case), or repeat visit (about 5% of the time). Can't store much info in cookies, as they are most likely to be using public computers. On Apr 12, 1:48 am, "Arun K.Rajeevan" <[email protected]> wrote: > Sorry to say I don't understand the scenario, > Out of curiosity why you need public users to be registered, if they are > happened to be some random visitor. > > Let everyone access the contents limited set of resources and allow only > registered users(*core*) to access the system fully; it's as simple as that.
