Identity Server - Identity & entitlement management. [Shib-Users] IDP Memcached StorageService implementation - Google 그룹스. (This message was sent initially to the dev mailing list, but I have found a similar topic (unsolved) at the users mailing list, so I think the audience for this issue may well be here at the Users Mailing List. Sorry for sending to both mailing lists) Hi, I am trying to write a Memcached based implementation of an IDP StorageService, to be able to run idp in 2 servers, without using Terracota.
I am running into trouble after the user authenticates successfully, right after attribute filtering: 11:55:19.784 - DEBUG [edu.internet2.middleware. shibboleth.common.attribute. filtering.provider. Open source - forgerock Identity Management Solution Vs WSO2 Identity Server. Shibboleth - Users - IdP Memcached StorageService implementation. > Hi, > > this may be an alternative to clustering the IdP 2.x with "Terracotta": > > During the past weeks we have been evaluating several methods to cluster > the Shibboleth IdP 2.3, and we would like to share our results with the > community.
We did some load testing and configuration optimizations on > our IdP nodes, and due to heavy resource load and performance issues > with "Terracotta", we decided to find a better solution for replicating > the IdP's state. Thus, we tested technologies like "Memcached", > "Infinispan" or "Hazelcast" and seem to have come up with a solution. > > Based on an old post [1], we have managed to implement a lightweight and > working IdP StorageService (this is the place where the IdP stores its > shared Objects) which connects to a Memcached server, along with a > servlet filter for post-processing each IdP request (see technical > details below).