<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    It includes the username of the admin.<br>
    <br>
    <div class="moz-cite-prefix">On 1/14/2016 2:50 AM, Stian Thorgersen
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAJgngAcoABvUNzn_Qhfe0fYqq+Gz-tk3ozAyHUT6DaHqnNbtJw@mail.gmail.com"
      type="cite">
      <div dir="ltr">So we already have an IMPERSONATE event? Does it
        include details about the admin?</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On 13 January 2016 at 22:29, Bill Burke
          <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">IMPERONATE
            replaces LOGIN event.  So, based on that you can just group<br>
            all events under a certain user session to the impersonate
            one.<br>
            <br>
            I changed my mind, I don't think this should be logged to
            the<br>
            console/log file by default.  The event manage can be set up
            to manage<br>
            all this.<br>
            <span class="im HOEnZb"><br>
              On 1/13/2016 4:16 PM, Marek Posolda wrote:<br>
              &gt; Wonder if impersonated events shouldn't be normal
              events, but just<br>
              &gt; have some prefix for them in type? For example
              IMPERSONATED_LOGIN,<br>
              &gt; IMPERSONATED_LOGOUT, IMPERSONATED_TOKEN_REFRESH etc.
              Similarly like we<br>
              &gt; have prefix in type for error events.<br>
              &gt;<br>
              &gt; And in all impersonated events, there might be also
              detail in the<br>
              &gt; event identifying admin user who is impersonating.<br>
              &gt;<br>
              &gt; Hopefully this is easy to implement without touching
              too much files in<br>
              &gt; codebase (but not sure) :)<br>
              &gt;<br>
              &gt; Marek<br>
              &gt;<br>
              &gt;<br>
              &gt; On 13/01/16 21:51, Bill Burke wrote:<br>
              &gt;&gt; IMO, impersonate events should not be treated as
              a success (debug) event<br>
              &gt;&gt; and should be logged to the console/log file. 
              Agreed?<br>
              &gt;&gt;<br>
              &gt;<br>
              <br>
            </span><span class="im HOEnZb">--<br>
              Bill Burke<br>
              JBoss, a division of Red Hat<br>
              <a moz-do-not-send="true"
                href="http://bill.burkecentral.com" rel="noreferrer"
                target="_blank">http://bill.burkecentral.com</a><br>
              <br>
            </span>
            <div class="HOEnZb">
              <div class="h5">_______________________________________________<br>
                keycloak-dev mailing list<br>
                <a moz-do-not-send="true"
                  href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
                <a moz-do-not-send="true"
                  href="https://lists.jboss.org/mailman/listinfo/keycloak-dev"
                  rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Bill Burke
JBoss, a division of Red Hat
<a class="moz-txt-link-freetext" href="http://bill.burkecentral.com">http://bill.burkecentral.com</a></pre>
  </body>
</html>