persistant nameid conflicting requirements

[Cantor, Scott]

> 	IdP 3.2.1 and persistant nameid generation conflicting requirement.
> 	I have a silly SP that needs a persistant nameid format but with the
> account uid in the value.

And you know this because? In most cases they are wrong about it anyway or can be pressured into doing it correctly. Make them deal with the one-off.
 
> Can I configure an override for that particular SP that generates a
> nameid with a custom persistant value ?

Yes, but you shouldn't and I very much doubt you have to. If you do, you should identify the vendor so people know about the issue.

> 	But IdP is still sending the calculated persistent nameid.

What you posted appears to be correct, assuming you put it in the appropriate order.

-- Scott