State Management and Clustering (IdP)
Christopher Bongaarts
cab at umn.edu
Mon Nov 12 11:47:04 EST 2012
On 11/11/2012 4:19 PM, Cantor, Scott wrote:
> On 11/11/12 4:59 PM, "Scott Koranda" <skoranda at gmail.com> wrote:
>>
>> 2) those sites needing "back-channel" support will be able to
>> leverage a clustering solution based on Infinispan that is
>> integrated into the IdP
>
> At the present time, we don't expect to have the time to work on that
> until some time after a first release. The focus right now is client side.
> Assuming that works (I'm not sure how to deal with the size limitations of
> cookies exactly), the main feature that really needs server side storage
> is some types of logout.
What sorts of limitations are known at the moment (in terms of what IdP
state is trying to be stuffed into the cookie)?
Anything where HTML5 client-side storage or ingenious compression
schemes for entityIDs could help?
> Speaking personally, I'm deeply skeptical of most clustering/replication
> technologies. I'm not a fan of asynchronous "best effort" replication, and
> most other types aren't very robust. I would be more comfortable with that
> for something like logout, that has no hope of being reliable anyway, than
> for mainline features like attribute queries.
I'm not quite as averse to clustering, but do strongly believe that the
less state you have to manage, the better.
--
%% Christopher A. Bongaarts %% cab at umn.edu %%
%% OIT - Identity Management %% http://umn.edu/~cab %%
%% University of Minnesota %% +1 (612) 625-1809 %%
More information about the dev
mailing list