a scripted attribute definition example from the wiki

[Peter Schober]

* Mark K. Miller <max at psu.edu> [2016-07-27 16:23]:
> I seem to be having some disappointing results with the code in the
> "examples" section at the bottom of a wiki page here:

Those came verbatim from a working test IDP I built, IIRC. Sorry if
those are not correct.

> I can get rid of most of the 'bad stuff' just by changing the end of the
> first line of the eduPersonPrincipalName definition to include this:
> 
> sourceAttributeID="eduPersonPrincipalName"
> 
> Really???  Is that really the correct fix?  That seems "too" easy!  How
> could that have possibly been left out of the example?  Should I just edit
> that example to include it?

I see it's thre in my local config, so I must have added it later and
forgot to add it to the wiki. I can do that and add a note about the
dependency warning this will trigger.

> However, even adding the sourceAttributeID info, and having a 'functional'
> attribute, every time the eduPersonPrincipalName is released the IdP still
> logs this message:
> 
> 2016-07-27 10:15:27,593 - WARN [net.shibboleth.idp.attribute.resolver.PluginDependencySupport:144]
>     - Plugin 'eduPersonPrincipalName' was defined with a sourceAttributeID
>       'eduPersonPrincipalName', but the attribute definition
>       'eppnFromUid', specified as a <Dependency> will be used as well.
> 
> Sadly, I have not found a way to eliminate this unwanted warning.  Can
> anyone tell me how to get rid of this?

What Scott said. From my logback.xml:

  <!-- Silence unavoidable dependency warnings -->
  <logger name="net.shibboleth.idp.attribute.resolver.PluginDependencySupport" level="ERROR"/>

-peter