Re: Permit only one network logon per user
- From: "Christian Thies [Ar]" <ch.thies@xxxxxxxxx>
- Date: Fri, 17 Aug 2007 11:52:11 -0300
Flibbitz, thanks for you answer
The domain is exclusive for sharing this service. I've tried to control
username and passwords in a non domain scenario, but I couldn't/don't know
how.
In the other hand, I am actually controlling a much demanded content. So
part of the contract users sign is that I control usernames and passwords
The domain can be removed if I can control access in a group environment
I´ll try the product FlexLM and let you know if fits to my needs
Regards
"flibbitz" <dum@xxxxxxxxxx> escribió en el mensaje
news:Xns998EE947EF575nspauac@xxxxxxxxxxxxxxxx
Are you trying to use the username that the users use to log into Windows
as your limiting factor, or is there a separate logon to your "product"?
If the latter, your product will have to maintain its own set of
usernames and passwords, and should handle limiting multiple logins
itself.
If the former, what is to stop (for one example) the same person from
logging in twice using different Windows usernames, and using your
product twice that way? It comes down to who is in control of creating
the usernames and how users are authenticated.
It sounds like you should "build your product" so that it handles this
itself, and not rely on altering the behaviour of Windows. No one I know
would be likely to buy a product if it required changes to their domain
like what you are asking for (except perhaps if they would use all the
computers in the domain for nothing but running that one product).
There are situations where there are reasons to limit the number of
simultaneous logins (such as in a school, to keep students from
"hogging" multiple computers in a shared lab, for example), and there are
products that provide this sort of function. However, I can't see much
desirability in this being done to control access to a single program.
Look at what many commercial programs/packages do - they often use their
own licencing system that controls who or what computers can run the
program, and/or limits the number of users/machines that can run the
program at one time. Actually, they often buy something like FlexLM
(among others) to include in their product for this sort of thing,
instead of creating their own licencing system.
"Christian Thies [Ar]" <ch.thies@xxxxxxxxx> wrote in
news:OJ2kARE4HHA.4436@xxxxxxxxxxxxxxxxxxxx:
I'm building a product that is accessed with a username and password,
and for preventing unauthorized access to it, I need to prevent
multiple simultaneous logons with the same username and password
Sorry about my English. Let me know if the answer is clear
Christian
"Steve Riley [MSFT]" <steve.riley@xxxxxxxxxxxxx> escribió en el
mensaje news:26CE53B9-E00D-4BB5-B2E2-17E5A305B4DE@xxxxxxxxxxxxxxxx
Why do you need to do this? What security risk do you need to
mitigate?
Steve Riley
steve.riley@xxxxxxxxxxxxx
http://blogs.technet.com/steriley
"Christian Thies [Ar]" <ch.thies@xxxxxxxxx> wrote in message
news:u71neA13HHA.5724@xxxxxxxxxxxxxxxxxxxxxxx
Hi, I have Windows 2003 domain working. I need to allow only one
network logon per user.
The example is:
User: username
Status: Logged
If user username try to login from a different machine, and he is
logged in another, the login attempt must be denied
How can I accomplish this?
Thanks in advance
.
- References:
- Permit only one network logon per user
- From: Christian Thies [Ar]
- Re: Permit only one network logon per user
- From: Steve Riley [MSFT]
- Re: Permit only one network logon per user
- From: Christian Thies [Ar]
- Re: Permit only one network logon per user
- From: flibbitz
- Permit only one network logon per user
- Prev by Date: Re: Permit only one network logon per user
- Next by Date: Re: Permit only one network logon per user
- Previous by thread: Re: Permit only one network logon per user
- Next by thread: Re: Permit only one network logon per user
- Index(es):
Relevant Pages
|
|
