v3.2 - unsupportable identifier -Name ID

[Cantor, Scott]

> There was no upgrade. It was fresh installation of V3.2.

That's why it broke.

> Commenting out
> idp.nameid.saml2.legacyGenerator helped the NameID specified.

You don't comment it out, you uncomment it and leave it enabled if you want it to leverage the old NameID encoders in the resolver, at which point it should work like it did before. Any problems at that point are related to the selection of the desired Format, which is documented in the wiki. That hasn't really changed from V2, but people have historically not done it correctly in many cases and are having problems with accidentally working systems no longer working because they weren't configured properly to begin with.

> I am still getting errors for NameID unspecified ones. Any idea?

You haven't described any error yet.

There are virtually no SPs that require that format anyway, when they claim to, they are almost always not checking it, which is fairly logical given that it means nothing.

-- Scott