https://community.splunk.com/t5/Security/How-do-I-ensure-one-active-session-per-user/m-p/496770#M11338 <P>Hello All,</P> <P>My goal is to stop users from sharing credentials (local authentication) which is a potentially useless endeavour, but I see two possible courses of action:</P> <OL> <LI><STRONG>ACTIVE</STRONG>: Set a limitation through a .conf (authentication.conf?) file that doesn't permit multiple sessions for a given local account</LI> <LI><STRONG>PASSIVE</STRONG>: Run a search to identify whether an account has more than 1 active session with successive witch hunt</LI> </OL> <P>Are either of these possible?</P> <P>Thanks!</P> <P>Andrew</P> Sun, 07 Jun 2020 20:08:03 GMT andrewtrobec 2020-06-07T20:08:03Z https://community.splunk.com/t5/Security/How-do-I-ensure-one-active-session-per-user/m-p/496770#M11338 <P>Hello All,</P> <P>My goal is to stop users from sharing credentials (local authentication) which is a potentially useless endeavour, but I see two possible courses of action:</P> <OL> <LI><STRONG>ACTIVE</STRONG>: Set a limitation through a .conf (authentication.conf?) file that doesn't permit multiple sessions for a given local account</LI> <LI><STRONG>PASSIVE</STRONG>: Run a search to identify whether an account has more than 1 active session with successive witch hunt</LI> </OL> <P>Are either of these possible?</P> <P>Thanks!</P> <P>Andrew</P> Sun, 07 Jun 2020 20:08:03 GMT https://community.splunk.com/t5/Security/How-do-I-ensure-one-active-session-per-user/m-p/496770#M11338 andrewtrobec 2020-06-07T20:08:03Z