Windows Authentication, storing user identity

  • Thread starter Thread starter Matt
  • Start date Start date
M

Matt

I am using Windows Authentication for a web application. I want to
store the identity of users who add, update and delete records in the
database. What is a good built-in active directory identifier to
use? Username, SID? I'd rather not use the username, because this
could change.

Thanks ~ Matt
 
I am using Windows Authentication for a web application. I want to
store the identity of users who add, update and delete records in the
database. What is a good built-in active directory identifier to
use? Username, SID? I'd rather not use the username, because this
could change.
Click to expand...

I would recommend to use the username, because it's a unique id in
AD.

If you cannot use it, consider a Globally Unique Identifier (GUID).
 
I would recommend to use the username, because it's a unique id in
AD.
Click to expand...

Username could change, right?
If you cannot use it, consider a Globally Unique Identifier (GUID).
Click to expand...

Are you talking about the objectGUID property from AD or creating a
mapping table?
 
Username could change, right?
Click to expand...

In my experience this happen very seldom.
You might also use a user's full name (Display Name)

Are you talking about the objectGUID property from AD
Click to expand...

Yes. GUID is never changed. SID can change and it is used only by
security principals.
 
Back
Top