storedID and IDP entityID changes

[Rod Widdowson]

> Necessarily the assertions Issuer wouldn't match
> the NameQualifier value then. Not sure if this will break stuff.

AFAIR the Prinicipal Connectors will reject the NameID/NameIdentifier if it
doesn't match what they are expecting.

> 
> If the IDP does not use the RDBMS abstraction layer for NameQualifier
> values why does it store its own entityID as localEntity then? 

At least notionally (I am not 100% up on the very grubby details of
RelyingParty.xml) you can configure an IdP (lump of java code sitting inside
a container) to have multiple entityIDs - and as such, I guess, act as
multiple SAML IdPs.  Certainly the data structures deep inside the IdP
understand the concept of multiple IdP EntityIDs.

Precisely what the use case is (apart from the obvious gun/bullet/foot
convergence) I'd not like to speculate on.

But the bottom line is that the IdP EntityId is not assumed to be a
singleton inside the IdP code.  Which is sort of like your case:

>  To allow sharing of a single table in a single database on a single
server across several IDPs?

You just have to change the meaning of "IdP"...

Rod