Building a composite attribute from sets of attributes

[Cantor, Scott]

On 8/7/19, 11:15 AM, "dev on behalf of Etienne Dysli Metref" <dev-bounces at shibboleth.net on behalf of etienne.dysli-metref at switch.ch> wrote:

> I'd prefer to have that script covered by unit tests, yet building a
> test harness to execute that bit of JavaScript the same way the IdP does
> is too complicated and brittle. That's why I favour Java, testing is
> easy. However, the less code the better, so if we get the same effect
> with much less JavaScript than Java I'll live with it...

I'm not opposed I guess to just putting together some kind of wacky JSON AttributeDefinition if we can make sense of the requirements for it, but I'm not sure it's got much general appeal.

We do have unit tests for scripted stuff, maybe we could help out there somehow.

Also, we could maybe come up with Java code to do part of the work, but leave it being run by the script.

What I was trying to say was that formalizing the concept of a new form of AttributeValue implies a great deal of plumbing all over the system.

-- Scott