User Login

  • Thread starter Thread starter Lars Netzel
  • Start date Start date
Hi Every one,

i have a login form which collect user and password from the user

And i would like to give the user an option to remember his user and
password for the next time.

what is the best way to save the user and password and where should i save
it ?

Thanks
T;-)
 
Depends on the application. If you have a multi-user / multi-homed app
(that is, it exists on several workstations sharing data, then use a
database like SQL, MSDE, or Access even (for smaller apps).

Of course Encrypt it as well. The registry is only really useful for
something machine specific or user specific such as program settings,
definatly not usernames and passwords.

-CJ
 
You *could* use a GUID for each user, but not for uniqueness. The username
itself should be unique. GUID's are often use to obscure data and make it
safer to pass it back and forth between forms and what not without moving
sensitive data.

So yeah, you could/should. Depends on how sensitive / secure your data is.
 
Hi,

should i keep some GUID for each user and when he will connect i will check
his GUID instead of user and password ?

Thanks.
 
Tiraman,

This sounds for me really unsave, something as that when there is a burglar
he can use the computer and logon, why not use the integrated roll based
security?

There is a sample in the resource kit.

I assume you have it or have the links?

I hope this helps?

Cor
 
Hi CJ,
I mean that in the first time the user put his user and password and he/she
will ask to remember it
I will do the login and I will create for him some GUID and this will be
saved in his computer
so in the next time I will check if there is already GUID in the computer
and so on ...

Thanks,
T;-)
 
Hi ,
It Sounds Good to use the integrated security but
I don't have the link for that :-)

Thanks
T;-)
 
See Cookie.


Tiraman :-) said:
Hi CJ,
I mean that in the first time the user put his user and password and he/she
will ask to remember it
I will do the login and I will create for him some GUID and this will be
saved in his computer
so in the next time I will check if there is already GUID in the computer
and so on ...

Thanks,
T;-)



CJ Taylor said:
You *could* use a GUID for each user, but not for uniqueness. The username
itself should be unique. GUID's are often use to obscure data and make it
safer to pass it back and forth between forms and what not without moving
sensitive data.

So yeah, you could/should. Depends on how sensitive / secure your data is.




Tiraman :-) said:
Hi,

should i keep some GUID for each user and when he will connect i will check
his GUID instead of user and password ?

Thanks.


"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
Depends on the application. If you have a multi-user / multi-homed app
(that is, it exists on several workstations sharing data, then use a
database like SQL, MSDE, or Access even (for smaller apps).

Of course Encrypt it as well. The registry is only really useful for
something machine specific or user specific such as program settings,
definatly not usernames and passwords.

-CJ


Registry, encrypted!

/Lars


"Tiraman :-)" <[email protected]> skrev i meddelandet
Hi Every one,

i have a login form which collect user and password from the user

And i would like to give the user an option to remember his user and
password for the next time.

what is the best way to save the user and password and where
should
i
save
it ?

Thanks
T;-)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Back
Top