User Authentication Issue: Need to Revert Two Users from ORCID to Built-in Authentication in Dataverse

[Alfredo Cosco]

Hello everyone,
I'm experiencing an authentication issue in a Dataverse instance with two users who have gone through multiple authentication method changes:

Background:
- Initially, both users registered as 'built-in' users
- I was then asked to integrate ORCID sandbox, so these users switched their authentication type to sandbox
- Subsequently, I was asked to implement the actual ORCID system
- Now both users want to revert back to 'built-in' authentication

Current Problem:

The two users have disappeared from the builtinuser table
However, they are still present in the authenticateduser and authenticateduserlookup tables
I cannot delete them because they have performed actions in the system
They cannot re-register because they exist in two of the three tables

Questions:

Can I manually insert two records directly into the builtinuser table to force their presence there?
If I do this, will the users become operational again?

Any guidance on the best approach to resolve this authentication conflict would be greatly appreciated.
Thanks,

Alfredo

[Philip Durbin]

Hi Alfredo,

From the user's perspective, they no longer want to log in via ORCID: https://guides.dataverse.org/en/6.7.1/user/account.html#convert-your-dataverse-installation-account-away-from-orcid-for-log-in

From your perspective as the sysadmin, you should follow this procedure: https://guides.dataverse.org/en/6.7.1/installation/oauth2.html#converting-oauth-users-to-local

Please let us know if you have any questions.

Thanks,

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/455e8b42-9d60-4ddd-9659-8a8a1a48969an%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Alfredo Cosco]

Thank you, Phil,

I tried running the command you suggested, but I'm getting this error: 

{"status":"ERROR","message":"User id 3 could not be converted from remote to BuiltIn. Details from Exception: java.lang.Exception: User id 3 (@user.identifier) cannot be converted from remote to BuiltIn because the email address users.id...@institution.it is already in use by user id 3 (@user.identifier). "}

The issue is that the user's email remained the institutional one even when they switched to ORCID authentication, and now they want to revert back to built-in.

I'm feeling a bit confused about how to proceed with this situation.

Could you provide some additional guidance on handling this email conflict during the authentication method transition?

Thanks again for your help.

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8EAkyAXyFL52tGLHQqrsyYS0vs1Agg_9z%2B4zpWfaUnR4Q%40mail.gmail.com.

[Philip Durbin]

Right, you're seeing https://github.com/IQSS/dataverse/issues/3834

Here's a workaround:

- When converting the account to builtin, provide an email address that you control and that doesn't already exist in the database.
- Reset the password for that email address.
- Change the email address to the one the user wants.
- Email the user and tell them to use the password reset feature.

I hope this helps!

Phil

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/CAB8fwFMuXfSXFZLcng5o_VfG6%2BnPtYq533tVYjetAxutePYofw%40mail.gmail.com.

[Alfredo Cosco]

Thanks Phil,
I'll try.
Alfredo