Stored persistent ID and migration to 3.2

Cantor, Scott cantor.2 at osu.edu
Mon Nov 23 09:54:20 EST 2015


On 11/23/15, 5:38 AM, "users on behalf of Simon Lundström" <users-bounces at shibboleth.net on behalf of simlu at su.se> wrote:



>On Fri, 2015-11-20 at 15:04:58 +0000, Cantor, Scott wrote:
>> On 11/20/15, 9:50 AM, "users on behalf of Simon Lundström" <users-bounces at shibboleth.net on behalf of simlu at su.se> wrote:
>> >Is that something you need to fix or for us deployers to configure?
>> 
>> You,
>
>Where should this be configured?

Sorry, I neglected to provide a reference to it in the docs. See the example box labeled "Example persistent ID store beans in saml-nameid.xml" in the updated PersistentNameIDGenerationConfiguration topic.

It's a collection property of the JDBCPersistentIdStoreEx class you wire up from the shibboleth.JDBCPersistentIdStore parent bean.

I'll add it to the example and adjust the docs since that's going to be a common need for a bit. It's better to have control of that bean anyway since you can adjust timeouts with it.

>>but we can collect up the codes we need to retry on and just add them to future versions too.
>
>Need an Jira for it?

I checked in this code already.

-- Scott



More information about the users mailing list