Configuring RemoteUser checkHeaders in IDP3

[Rich Graves]

> That configuration file is for RemoteUserInternal, not RemoteUser.

Done, thanks! We now have the subject. Which for uninteresting reasons is
scoped, and we need the unscoped username for attribute resolution purposes.

Now how can we strip the domain, returning just username? I.e., for
RemoteUser, where would I stick this? In IDP 2.x, you could define
principal as an attribute and hack at it there, but does that still valid
in 3.0?

    <util:list id="shibboleth.authn.RemoteUser.Transforms">
        <!--
        <bean parent="shibboleth.Pair" p:first="^(.+)@example\.edu$"
p:second="$1" />
        -->
    </util:list>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160713/7777b501/attachment.html>