SP client-side session storage and originating IdP

[Wessel, Keith]

Hi, all,

We've been looking at the new SP client-side storage as an option for making more horizontally scalable containerized applications running in AWS. In hopes of avoiding a database or Memcache instance, we're looking at the new cookie storage that SP 3.0 offers.

The docs say that you provide a list of attributes that you want to store in the cookie. I assume these are attribute friendly names as configured in the attribute map.

I'm wondering what other non-attribute information gets stored in the cookie. Specifically, will another clustered SP node know the IdP that generated the assertion to be able to initiate a federated logout?

Thanks,
Keith