Efficiency in AttributeDefinitions

[Bennett, Steve]

> Are you sure the NameFormat is unspecified? It might also be "basic".
> Just saying.

That's what the vendor docs say... and it works as it is.

> The current IdP does not do conditional resolving, yes.
>
> There are some hacks to make it do that, if you really want to (check the list archives)
> and already have the numbers that prove it's necessary

I'm not particularly keen to start hacking the IdP just yet. I don't have any figures to demonstrate a need since our IdP see quite low traffic and certainly has no performance issues, but I wanted to confirm that I wasn't missing any obvious tricks.

> If the SP requires three different attributes that's the /only/ way, of course.
> If you're asking of whether the IdP has some "batch" type feature
> that would allow the creation of multiple attributes in one go, then no.

> In this case my answer would be clearly no, you shouldn't care about the
> overhead of attribute definitions that take existing (i.e., already resolved)
> attributes and making them available under different names.
> Even if there's a regex in the telephoneNumber case ;)

That's just I was hoping to hear :-)

Thanks!!

Steve.