Login and password

[curiousvbnet]

I ma working on the login and password keyboarding and the verification of each one.

Do you advice me to create a table with administrators profiles only and another one with users profiles only or is it also a good solution to create a unique table with both administrators and users profiles ?

If you create a unique table, how can you recognize a profile is a user profile or an administrator profile?
Do you need another field for this?

When you update a profile, do you have to give a user to change its password and also its login or is it better to give him the possibility to change only the login or only the password .


Thanks a lot for your help because i have to finish with the login and password update.

Best regards.
Nathalie

 

[SiriusBlackOp]

Use the same table, and yes, add a field to the table to indicate which group the user is a member of.

Typically systems do not allow the users to change their own logins, but if yours will... changing both on the same page should be fine, but after they do it may be a good idea to log them out and force them to log back into your app just to clean things up.


Senior Software Developer

http://www.scoutsft.com

 

[curiousvbnet]

Hi and thanks a lot for your help.

So tou advice me not to allow to change the login but only the password, and if the users want it, it is better to propose them to change in the same tim login and password in a same form.

I don't understand well what you mean by "it may be a good idea to log them out and force them to log back into your app just to clean things up."

If you could explain me what you meant, it would be very kind from you.

Thanks a lot for your help.
Regards.
Nathalie

 

[SiriusBlackOp]

If you allow user-1 to change their user name to something like user-2, and you had previously stored the username in RAM during their login process for use throught your program, then it can sometimes be easier to log them out at the end of the change username process to reset the user data stored in RAM.

The other thing that is good practice to avoid is duplicate user names.

Senior Software Developer

http://www.scoutsft.com

 

[curiousvbnet]

Hi and thanks a lot for your advice.
So you mean it would be better to propose the user to relogin after he has changed his login and password ,and so, to get out of the application and to enter a new time.

Do you think that if the user does not relogin just after he has changed its password or login it can provoke something wrong , perhaps at a security level.

thanks a lot for ypour help.

Regards.
Nathalie

 

[SiriusBlackOp]

It depends on what you are doing with the login information and how you are storing it.

If you don't ever do anything with the user name, then it probably doesn't matter.

Test your application by using it, changing the user name, and then using it some more. If it breaks or uses the old username in the last half of the test, then you will either need to fix it or have/force them log out and back in.

Senior Software Developer

http://www.scoutsft.com