Scripted Attribute resolution and legacy support.

[Tom Zeller]

> 1) Change the name that the scripting sees for the V3 resolution context so
> that we make the emulated V2 one available via the old name (done).

Could you point me where this was done ?

In IDP-206 I see the following, but I don't understand :

1) Rename the (Native, V3) resolutionContext to be "resolutionContext"
such that "requestContext" can be used for legacy (V2) scripts


> 3) Provide a helper object to ease (V3) context navigation (basically to go
> from a string to a java.lang.Class which can then be fed into the context
> navigation code).

I think I even mentioned the context navigation helper for other
reasons, curious how it turns out.


> 4) Add a vestigial
> edu.internet2.middleware.shibboleth.common.attribute.provider.BaseAttribute
> with one method: Collection<String> getValues. [*]
> [*] this class represents a difficulty - do we want to put it inside
> idp-attribute-resolver-impl (which is a bit ugly) or do we want to give it
> its own jar (which is overkill).  Opinions?

As we chatted, the v2 BaseAttribute might have a long life in scripts
if we provide backwards compatibility. Wondering if an
idp-v2-compatibility module might contain such things.