Where to hook in switching of user identity

[Christopher Bongaarts]

On 6/24/2016 2:31 PM, David Langenberg wrote:
> So, with all this spoofing stuff, how do you deal with non-repudiation of the spoofed accounts for auditors?  Did you modify the logs/assertion to sufficiently indicate to the SP and/or within the IdP that the particular authN event is being spoofed by a particular identity?

In our case, the spoofing mechanism is intended to be an improvement 
over forcing a bunch of end users to share their passwords with testers :)

Some of the policy/procedure controls around this function:
- Access request process for testers to be authorized for using spoofing 
(limits set of accounts that can be used to spoof)
- Separate IdP instance that only supports spoofing (so unauthorized 
users cannot log in at all)
- SPs must be specifically configured to use the spoofing IdP, 
minimizing the scope of SPs able to be spoofed into
- The spoofing IdP uses our test LDAP instance, so testers need to 
request that their targets be populated there
- The spoofing IdP logs both the spoofer and the target to a 
(proprietary) audit log, e.g.
YYYY-MM-DD HH:MM:SS,uuuuu login ok for cab as target01 on 
https://sp.example.org/

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%