Upgrading from 5.1 to 5.3 with JPA service registry and SAML 2 services

14 views
Skip to first unread message

Richard Frovarp

unread,
Feb 5, 2020, 6:36:51 PM2/5/20
to CAS Community
Looks like there was a change to how SAML 2 services were defined in CAS
5.2. So when Hibernate brings those back in, it's failing to create the
object. My guess is that since there isn't anything there in the
serialized form, it is trying to set a boolean to null, which doesn't
work well for primitives. I haven't been able to find any upgrade
instructions to handle this. Are there any? Or are we going to need to
delete our SAML 2 services first, and then recreate?

org.hibernate.PropertyAccessException: Null value was assigned to a
property [class
org.apereo.cas.support.saml.services.SamlRegisteredService.skipGeneratingAssertionNameId]
of primitive type
setter of
org.apereo.cas.support.saml.services.SamlRegisteredService.skipGeneratingAssertionNameId


Thanks,

Richard

Richard Frovarp

unread,
Feb 5, 2020, 6:52:52 PM2/5/20
to CAS Community
While trying to figure out how to delete just the SAML 2 services to
prepare for that, I saw the new fields were added to the DB instead of
being in one of the serialized fields. So this worked, getting me to
defaults:

update regexregisteredservice set
skipGeneratingAssertionNameId=0,skipGeneratingSubjectConfirmationInResponseTo=0,skipGeneratingSubjectConfirmationNotBefore=1,skipGeneratingSubjectConfirmationNotOnOrAfter=0,skipGeneratingSubjectConfirmationRecipient=0,skipGeneratingTransientNameId=0
where metadataLocation is not null;
Reply all
Reply to author
Forward
0 new messages