Migrate invalid unspecified NameID

Question

Migrate invalid unspecified NameID

relaxnow opened this issue 10 years ago · comments

In the past the invalid 'unspecified' NameID was used and it should be migrated.
From: 'urn:oasis:names:tc:SAML:2.0:nameid-format:unspecified';
To: 'urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified';

Boy Baukema · Answer 1 · Tue Jan 13 2015 20:14:31 GMT+0800 (China Standard Time)

Requires manual migration

Thijs Kinkhorst · Answer 2 · Tue Mar 31 2015 15:31:52 GMT+0800 (China Standard Time)

We are now migrating our own apps. Then we'll approach the affected external SP's.

Thijs Kinkhorst · Answer 3 · Thu Jul 09 2015 22:05:34 GMT+0800 (China Standard Time)

Everything has been migrated away. This value can be removed from Janus. A migration is not needed because this has already been completed and it's a SURFconext-specific error.

Thijs Kinkhorst · Answer 4 · Fri Jul 10 2015 22:25:04 GMT+0800 (China Standard Time)

For Janus this is config-only. The configuration has been updated in the deploy repository. This issue can therefore be closed.