How do I maintain same instance of an application for all the windows LDAP users

Question

0.00/5 (No votes)

See more:

There is very interesting requirement from the client. Clients wants to maintain same instance of an application for all the windows LDAP users, when LDAP user logged in on their own session on same windows machine using their own credentials.
That means if suppose user 'A' is using one application on one machine and left the machine with locked position, and after that user 'B' comes and unlocked the machine by his own credentials then he can continue to use the application from the same state where user 'A' is left the application running.

What I have tried:

Trying to search for the solution available on the site, so far not seen any solution.

Posted 18-Feb-20 14:38pm

SupportICS

Updated 18-Feb-20 16:23pm

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2020-02-18T14:55:00

Windows doesn't support doing this. Supporting such would be a massive security risk.

The process is owned by and has a copy of the security token from the account that launched it. UserB will never have the same instance that UserA started. The process runs AS THE USER that launched it with the exact same security permissions. It's not possible for UserB to "take over" a process once it's been launched by UserA.

The only way this "requirement" is going to work is if all users on the machine use a shared ID and password.

MadMyche · Answer 2 · 2020-02-18T16:23:00

Solution 2

About the only way to pull this off is to have a server based application and a (mighty) thin client running on individual machines, and utilize the "Machine" account

Posted 18-Feb-20 16:23pm

MadMyche