When testing Federated Authorization for Dataset Browsing and File Download I ran into a problem where an account from staging had logged into staging2, but had a different openid then what was present in the database for staging2, but the UUID was the same. So a database constraint was thrown because the OpenID consumer code in the MyOpenID4JavaConsumer class didn't find the user by openid, but did try to insert the user as new but with a uuid that was already in the database.

It would be better if a more informative error message was given to explain the issue.