Nameid unspecified with Legacy Relying party
Cantor, Scott
cantor.2 at osu.edu
Mon Mar 20 20:12:35 EDT 2017
On 3/20/17, 7:38 PM, "users on behalf of Ramaiah, Vanna G." <users-bounces at shibboleth.net on behalf of ramaiah at musc.edu> wrote:
>I upgraded from v2.4 to v3.3. Everything seems to be working fine except for “unspecified” nameids.
Then your old configuration was broken to start with.
> How to solve the nameids unspeficied problem.
The chances are you don't need them. If you actually do (you don't), then you configure them properly, by setting the nameIDFormatPrecedence property in the relevant profile configuration. Same as before. Follow the V2 documentation if you're using the legacy format.
> While I contact the SPs to change the nameids format specified, I am afraid that cannot happen soon.
Just stop using them and the SP will most likely not even notice.
> Here is relying-party sample.
It doesn't include the nameIDFormatPrecedence setting. There is no other way to correctly select that Format, so your old file was broken, and that's why the upgrade failed.
https://wiki.shibboleth.net/confluence/display/IDP30/UpgradingFromV2
The documentation explicitly calls this out.
-- Scott
More information about the users
mailing list