Double entityid attributes about thiss-js HOT 7 CLOSED

Confirmed. I'm pretty sure the issue is in cta/index.js where we only look at entityID instead of using that as a fallback.

from thiss-js.

I've pushed a PR - can you test integration with https://deploy-preview-137--thiss.netlify.app/ and tell me if you can see any issues?

from thiss-js.

Hey Leif,

I can still see both attributes present in the storage (some identifiers removed):

{ "last_refresh": 1615304223944, "last_use": 1615304223944, "entity": { "title": "MY ENTITY", "descr": "MY ENTITY", "title_langs": { "en": "University of ..." }, "descr_langs": { "en": "University of ..." }, "auth": "saml", "entity_id": "urn:...", "entityID": "urn:...", "type": "idp", "hidden": "false", "scope": "MY SCOPE", "domain": "MY SCOPE", "name_tag": "GTY", "id": "{sha1}..." } }

I would expect to see only entity_id - is that correct?

from thiss-js.

No you should still see both attributes. My fix simply deals with both of them in the standard integration.

from thiss-js.

Does it mean, if a service provider sets up only entity_id attribute (using advanced implementation) and another service provider uses standard implementation persistence service should work both ways between those service providers?

from thiss-js.

yes that is the idea

from thiss-js.

OK I'm gona mark this as closed. It will get rolled out to testing with a bunch of other stuff.

from thiss-js.