To answer your question, no there is not.

What you might want to check is whether you can use the Envers Query API to obtain the data you're after in the short-term rather than using the Spring wrapper to accomplish the task. This would allow you to avoid this problem entirely and supply your own custom revision type to support identity-based identifiers.

I do see that the issue is being fixed by https://jira.spring.io/browse/DATACMNS-1290, so that's promising.