Feature Request/Idea: When a user is a shib user and they issue a password reset request, send them an email saying they signed up with uni credentials.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
When a user is a shib user, they may forget that they either created their account as shib, or converted it from local to shib, and try to login with what they believe to be their valid local email/password account. When that doesn't work, they then request a password reset but nothing happens in Dataverse - no message, no email, etc. so the user believes there is something wrong. And then the user emails the Dataverse installation's support team, creating an access delay for the end user and creating more tickets for the support team.
So when a user issues a password reset, if they are a shib user, send them an email saying so and with instructions on how to login as a shib user.
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?
A few times a week ADA receives an email from a user saying their password no longer works and they are not receiving a password reset email when they issue a password reset. The majority of times the user is a shib user.
What existing behavior do you want changed?
If a password reset is requested and the user is a shib user, send them an email saying they are a shib user and to choose their Institution to login with those credentials. This will give them an immediate answer to how to get access, and will reduce the number of emails/tickets sent to the Dataverse installation's support team.
Any open or closed issues related to this feature request?
Not that I can see.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the password reset request flow and the handling of Shibboleth users. Determine where reset requests produce no response for these accounts, then define the email content and login instructions with maintainers. Add coverage for the Shibboleth password-reset case and verify the existing local-account behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100