Hello, I have a workaround for this, that is not to be considered a permanent solution but shouldn't have bad side effects.
You could simply add the package
ca.uhn.fhir.jpa.searchparam.config to spring component scan, for example in application.yaml:
It contains class NicknameServiceConfig that creates the needed Bean.
The only other class in the same package is
SearchParamConfig which is hard-imported by class ca.uhn.fhir.jpa.config.JpaConfig.
Hope that helps.