Migration issues with shibboleth.JPAStorageService to JDBCStorageService

[Cantor, Scott]

> now the new datasets differ, so that existing entries are not valid anymore. 

They are supposed to be identical and I don't think there's any past indication that they're not.

> This results in user consent to pop up again - and some nasty json-parsing
> exceptions.

That would be a bug, and I don't really believe that's true. We have other issues with sorting that cause that, but nothing storage-driven.

> As you can see the value-field now holds a JSON object and is not
> compatible to the old values - whatever they represent. 

We have always, mostly, stored data in JSON, that's not a new thing.

-- Scott