IQSS / IQSS/dataverse

Feature Request: Provide config param to require email be verified before users can request access, download files.

Open
#11,719 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Feature
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
Require email be verified before users can request access, download files.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)

All users.

What inspired the request?

The ADA access team spends A LOT of time checking that users who have requested data have verified their email address, have to email them to do so if they haven't, recheck it, etc. This is a considerable amount of overhead.

What existing behavior do you want changed?

Currently, a user doesn't have to verify their email address at any point - they can just request access and download files when given access.

If a verified email is required, there is a lot of overhead associated with all the checks and comms between the data custodian/owner and the users. This overhead could be eliminated.

Any brand new behavior do you want to add to Dataverse?

Provide a flag per dataverse installation that when set to true requires a user to verify their email address either full stop (they have to verify it before they can proceed with anything in the dataverse ui or api), or when they request data and when they go to download data (if their email is not verified, they can't request and they can't download).

Any open or closed issues related to this feature request?

Not sure.

Are you thinking about creating a pull request for this feature?

No resources to do so.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing email-verification flow and the authorization paths for access requests and file downloads. Define the installation-level configuration behavior and decide whether enforcement applies throughout the UI and API or only to requesting and downloading; done means unverified users are blocked in the selected scopes and verified users retain access.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authentication, authorization, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.