rdmorganiser / rdmorganiser/rdmo

Unable to reject Terms of Use / delete user data

Open
#1,627 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:feature-request
Dominant language
Python
Stars
133
Forks
60
Avg merge
3d 14h
Merged PRs (30d)
21

Description

Description / Beschreibung

We would like to include Terms of Use into the workflow of our RDMO installation. We are using SSO via Shibboleth, ORCID and local accounts.
After logging in via SSO, a local user account is created and the Terms of Use dialog is shown with a checkbox and a button for accepting the ToU.
Now it is generally not possible to reject the ToU. When navigating to RDMO the user is repeatedly shown the ToU dialog. There does not seem to be a way for the user to delete the account that had been created automatically (and which is also necessary to track the state of agreeing to the ToU).

Expected behaviour / Erwartetes Verhalten

Ideally, agreement to the Terms of Use should be required before SSO is started so that no user account is created at all in case the ToU are rejected. Alternatively, there should be an option to reject the ToU after SSO login which deletes all user data that has been stored as consequence of the SSO procedure.

Steps to reproduce / Schritte zum Reproduzieren
  1. Enable SSO.
  2. Enable Terms of Use.
  3. Log in and see described behaviour.
Context / Kontext

OS Debian Trixie
RDMO 2.4.4

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 with the linked Shibboleth SSO and Terms of Use middleware documentation, then trace the login and ToU flow described in the issue. Done means rejecting the ToU does not leave the automatically created account or stored SSO-derived user data, with the three reproduction steps confirming the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
authentication, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.