Deprecated IdPV4 Warning - Custom DataConnector
Reid Watson
reid.watson at auckland.ac.nz
Wed Aug 21 02:00:22 EDT 2019
Hi Everyone
On our IDP 3.4.1 were looking at addressing the “ Deprecated Warnings” before 4.0 is released, we currently have a custom DataConnector for ElasticSearch and I was hoping for some advice.
Warning Message
Java class 'nz.ac.university.shibboleth.common.config.attribute.resolver.dataConnector.HibernateDataConnectorBeanDefinitionParser': This will be removed in the next major version of this software; replacement is nz.ac.university.shibboleth.common.config.attribute.resolver.dataConnector.HibernateDataConnectorBeanDefinitionParser
Current DataConnector
<resolver:DataConnector id=“Test" xsi:type="Hibernate"
xmlns="urn:mace:university.ac.nz:shibboleth:resolver:hibernate"
something="XXX"
searchServer="%{search.Server}"
identityTypeName="%{search.identityTypeName}"
searchIndexName="%{search.searchIndexName}">
</resolver:DataConnector>
I see two options but please correct me if I’m wrong
- Investigate migrating the current DataConnector to IDP v4 standards for example “Native Spring Configuration” — I will need to understand the plugin types to support my required connection
- Switch the plugin type from hibernate to HTTP - There would be a bit of effort in formatting the data and QA testing
Has anyone else run into a similar problem and keen to share any thoughts ?
Cheers
Reid
More information about the users
mailing list