You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Dataverse configuration sets up an OIDC Provider, but it doesn't add a row to authenticationproviderrow, there for the user is not visible in the Dataverse Dashboard ->Manage Users View.
What steps does it take to reproduce the issue?
Step 1: Run the Development Environment
Execute npm i.
Navigate with cd packages/design-system && npm i && npm run build.
Return with cd ../../.
Ensure you have a .env file similar to .env.example, with the variable VITE_DATAVERSE_BACKEND_URL=http://localhost:8000.
After the first login, you will be redirected to finish the registration process, where you will have to accept the terms (although there are none for now) and you will also be able to optionally add the affiliation and position.
After submitting the form, you will be redirected to the “root” collection page with a welcome success alert and some confetti. 🎉 .
After the user has been registered, go to the JSF frontend and login as dataverseAdmin. Go to Dashboard -> Manage Users view. The newly created user is not displayed, only the Dataverse Admin.
Related Issues
An related issue has been created for this in Dataverse: IQSS/dataverse#11090
The text was updated successfully, but these errors were encountered:
The Dataverse configuration sets up an OIDC Provider, but it doesn't add a row to authenticationproviderrow, there for the user is not visible in the Dataverse Dashboard ->Manage Users View.
What steps does it take to reproduce the issue?
Step 1: Run the Development Environment
Step 2: Test the feature in the SPA
Related Issues
An related issue has been created for this in Dataverse: IQSS/dataverse#11090
The text was updated successfully, but these errors were encountered: