Home/ Questions/Q 64313
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T18:46:13+00:00

When designing user table what would be the must have fields from the security/user

  • 0

When designing user table what would be the must have fields from the security/user authentication point of view for a Web based Application (.NET and SqlServer 2005)

I came with with the following fields:

userID username -- preferably email passwordHash  onceUsePassword -- to indicate that the password should be changed after login alternativeContactEmail  userStatusID -- FK to a lookup table with statuses like: active, diabled etc  dateCreated dateUpdated lastPasswordUpdate lastLogon -- and then the rest like :forename, surname etc which are not of the interest in this question

Am I missing something?

Is standard identity (INT) sufficient for userID or should the GUID be used instead (the userID is not going to be exposed anywhere)?

EDIT:

  • I am limited to the use of .NET 1.1 (don’t ask…)
  • The salt info will be merged with passwordHash
  • the account would be unlocked by sending a temporary, single use system generated password to the user email address (hence onceUsePassword field)
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Why not just use the built-in SQL Membership Provider if you’re using SQL Server anyway? It’s much better than rolling your own since it’s been tested by a lot of people.

    In any case, you should think about adding a salt field your table.

    Salting

    Update: .NET 1.1? I guess that answers my question. Is your application for the consumption of the general public? If so, you might want to add a way for them to unlock their accounts via a secret question.

    • 0