Validating Users

[=?Utf-8?B?anAybXNmdA==?=]

Some of our apps need passwords to access parts that should only be available
to management.

We could develop our own and require management to remember yet another
password that we would have to take care of resetting whenever they forget,
lock themselves out, or whatever...

But, what if we could tap into the Windows Login? Can that be done?

Here's what I'm thinking:

Call a login box (ours or Windows') and have them enter their username and
password. If the username/password combination matches, we activate features
if they are in management.

I don't really need to know how the Windows Login works - I would just like
to call it and get the results.

Can that be done? If so, how? If not, what is another solution (besides
reinventing the wheel)?

[rowe_newsgroups]

Re: Validating Users

On Aug 29, 2:56 pm, jp2msft <jp2m...@discus sions.microsoft .comwrote:

Some of our apps need passwords to access parts that should only be available
to management.
>
We could develop our own and require management to remember yet another
password that we would have to take care of resetting whenever they forget,
lock themselves out, or whatever...
>
But, what if we could tap into the Windows Login? Can that be done?
>
Here's what I'm thinking:
>
Call a login box (ours or Windows') and have them enter their username and
password. If the username/password combination matches, we activate features
if they are in management.
>
I don't really need to know how the Windows Login works - I would just like
to call it and get the results.
>
Can that be done? If so, how? If not, what is another solution (besides
reinventing the wheel)?

If you don't need to worry about the password you can use
Environment.Use rName to get the logged-in user. That makes the
assumption that if they've logged into Window's they are good-to-go.
It will not protect you if the user doesn't lock his computer and
someone else steps in and uses it.

Thanks,

Seth Rowe [MVP]

http://sethrowe.blogspot.com/

[=?Utf-8?B?anAybXNmdA==?=]

Re: Validating Users

Everyone in management has their own PC; however, on the production floor,
all PCs log in using a common ID ("public") which has limited company network
access and no Internet. This ID is always running on about 150 PCs.

I've been doing some searching, and it looks like I might be able to query
Active Directory for this information, but I've got to do some research. We
have it, but I've never messed with it.

"rowe_newsgroup s" wrote:

On Aug 29, 2:56 pm, jp2msft <jp2m...@discus sions.microsoft .comwrote:

Some of our apps need passwords to access parts that should only be available
to management.

We could develop our own and require management to remember yet another
password that we would have to take care of resetting whenever they forget,
lock themselves out, or whatever...

But, what if we could tap into the Windows Login? Can that be done?

Here's what I'm thinking:

Call a login box (ours or Windows') and have them enter their username and
password. If the username/password combination matches, we activate features
if they are in management.

I don't really need to know how the Windows Login works - I would just like
to call it and get the results.

Can that be done? If so, how? If not, what is another solution (besides
reinventing the wheel)?

>
If you don't need to worry about the password you can use
Environment.Use rName to get the logged-in user. That makes the
assumption that if they've logged into Window's they are good-to-go.
It will not protect you if the user doesn't lock his computer and
someone else steps in and uses it.
>
Thanks,
>
Seth Rowe [MVP]

http://sethrowe.blogspot.com/

>

[Michel Posseth [MCP]]

Re: Validating Users

You should add roles ,,, and query the User.IsInrole method to grant access
to certain parts of the program

http://msdn.microsoft.com/en-us/library/microsoft.visualbasic.applicationservices.user.isinrole.aspx

HTH

Michel



"jp2msft" <jp2msft@discus sions.microsoft .comschreef in bericht
news:F1400DC5-B3FF-4D00-A103-A9F1D39F4941@mi crosoft.com...

Everyone in management has their own PC; however, on the production floor,
all PCs log in using a common ID ("public") which has limited company
network
access and no Internet. This ID is always running on about 150 PCs.
>
I've been doing some searching, and it looks like I might be able to query
Active Directory for this information, but I've got to do some research.
We
have it, but I've never messed with it.
>
"rowe_newsgroup s" wrote:
>

>On Aug 29, 2:56 pm, jp2msft <jp2m...@discus sions.microsoft .comwrote:

Some of our apps need passwords to access parts that should only be
available
to management.
>
We could develop our own and require management to remember yet another
password that we would have to take care of resetting whenever they
forget,
lock themselves out, or whatever...
>
But, what if we could tap into the Windows Login? Can that be done?
>
Here's what I'm thinking:
>
Call a login box (ours or Windows') and have them enter their username
and
password. If the username/password combination matches, we activate
features
if they are in management.
>
I don't really need to know how the Windows Login works - I would just
like
to call it and get the results.
>
Can that be done? If so, how? If not, what is another solution (besides
reinventing the wheel)?

>>
>If you don't need to worry about the password you can use
>Environment.Us erName to get the logged-in user. That makes the
>assumption that if they've logged into Window's they are good-to-go.
>It will not protect you if the user doesn't lock his computer and
>someone else steps in and uses it.
>>
>Thanks,
>>
>Seth Rowe [MVP]
>http://sethrowe.blogspot.com/
>>