Creating login Credentials for 20,000+ users

[Gustavo1478]

Hello world, I have an existing web app that we (we = administrative staff) use at our school for data entry which tracks all classes and current status for all of our students.

I would like to extend access to all of our students using the alpha web security but I'm a bit at a loss of how the best way of doing this is. We have more than 20,000 students in our database and I want to create a login page that uses their StudentID# as username and their SSN as the password.

One way I thought of doing this was to create a separate application for students only, and have them register with the new blank web security tables that are separate from the administrative users.

So on the pre-built alpha ux registration component do some kind of look-up to see if the student exists then just have them verify all the personal info that we have on file for them and submit the form then redirect to a portal where they can manage their personal info and see how they are doing etc., and if the user does NOT exist, Send them to a blank page that will enter them insto our existing system.

Im asking this question to get some input from professionals before I begin on this massive quest, I dont want to be a month into this project and find out there was an easier way of handling this. Any and all feedback is welcomed.

[mikeallenbrown]

Re: Creating login Credentials for 20,000+ users

I think you could do all of this in SQL with just a few statements. You can even create the GUID in SQL. You just need the right data in those security tables and all students would then be "registered".

These students will be accessing the same app that the administrators have access to?

[Gustavo1478]

Re: Creating login Credentials for 20,000+ users

Yes I think I can create it using SQL also with statements, but not all students would be logging in since some have graduated and moved on, Plus I want to create a registartion page for students who are not currently students.

Students will be accessing a similar but completely separate components with different security settings (I plan to use the TabbedUI).

Ive already started, technically,I let alpha create the web security tables for me. One of my Main concerns, well two of my main concerns is, (1) can the alpha server handle that much traffic (we have 2,000 active students currently) (2) Is using the builtin alpha security more secure than something I would be able to create with out it.

I dont know how to build ux's without alpha, any suggestions here?

[mikeallenbrown]

Re: Creating login Credentials for 20,000+ users

I see. I think a registration page is the way to go. I would use a SQL store procedure to handle the creating of records in the security tables (I like to handle that part myself. Personal preference). Not sure of how secure you need the accounts to be. In my apps users need to provide a valid e-mail. That e-mail is then verified through a link I create and send in an e-mail to the user. I also have my users create security questions for when they loose their passwords. Passwords are hashed and salted. Too much liability when you storing personal info like social security numbers. The app and it's security needs to be air tight.

I think Alpha can handle that many users. Not all of them will be logging in and using the app all at once. With that many users you may need to purchase another app server or two and then use a load balancer but you'll need to feel that out. Also, you can run multiple instances of the same app server. In one app I support I have six instances across two separate app servers (using a load balancer). That app has around that many users too but only a small percentage is ever on at once.

[Steve Wood]

Re: Creating login Credentials for 20,000+ users

Totally wrong approach. SSN as the password? DON'T DO IT! In addition to that being personal private information. YOU should not know the user's password.

Now that I got that out of my system, it is still the wrong approach to pre-register all of those users. If your place is typical, you will add 20,000 users and some 10% will ever use it, and the 90% will just sit idle, waiting for someone to hack it. Instead, put zero people in the security system. Add them instead to a User table with their name, and other information, and a GUID for each user (don't use a sequential value as the ID for users). Then send them all an email with a time-sensitive link (a like that only works for maybe a week) telling them to click to register. By when they register, do a double opt-in process, meaning you send them back an email after they register and ONLY when the click on a second time sensitive link in that email, do you add them to the security system, and they can login from that point on.

The built in security is great, no reason not to use it.

The app server can handle 2000 users IF they login and use the system throughout the day. But if they all are going to use it at the same time, it won't work without additional resources, multiple Alpha instances, etc.

Here is an article written in 2002 about why you should not use SSN as the password, and other sins: http://usatoday30.usatoday.com/tech/...-privacy_x.htm