IDP 3 clustering

[Cantor, Scott]

> > That's a V2 thing, not a V3 thing.
> 
> We are currently running IDP 2.4.

Then why does the subject line say IDP 3 clustering?

> According to Pete Schober's reply earlier,
> this has been brought forward to IDPv3.  Now I'm confused.

The functionality is there, that doesn't mean you need to apply deprecated settings and options. 

> I'm not sure I understand what you mean.

I mean, stop doing things. If you upgraded a V2 IdP that was not using the crypto plugins for clustering use, then these settings won't be there and won't be needed. If you're starting from scratch, they're also not needed. So either way, not needed.

> Our IDP releases transientid by default.

transientID is no longer an attribute you need to release at all. Any references to it in the resolver are deprecated and no longer needed. They won't hurt anything, but they won't be used either.

>  I added "Crypto Transient ID Attribute definition" in attribute-
> resolver,  but if I don't release it in attribute-filter, how does the SP use
> cryptoTransientId?

Take a look at the NameID generation documentation in the wiki. With respect to how queries are handled, that's discussed in the NameID consumption documentation.
 
For transient support, all of this is installed by default now, and has nothing to do with attributes anymore because this is not an attribute at all, it's a NameID type.

-- Scott