IQSS / IQSS/dataverse

Grant API rights to Shibb group members

Open
#10,702 0 comments 1 reaction 0 assignees View on GitHub

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
User permissions on a dataset or a dataverse collection granted via Shibboleth group do not translate to API permissions.
Here is a proposal to be able to grant them API rights identical as the UI's while taking into account that a Shibboleth user can be removed from a federation while its token remains valid :
https://docs.google.com/document/d/1RNjTmdf5vDe4KnvyjlHb4a_HHdwKnRC7FLIfzZJ9I8Q/edit?usp=sharing

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

What inspired the request?
Our use of Shibboleth group to give defaults rights to our collection (see the Background section of the proposal)

Any brand new behavior do you want to add to Dataverse?
Grant API access to Shibboleth group members if they are still active.

Any open or closed issues related to this feature request?

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 reading the linked proposal and comparing its requirements with Dataverse's existing UI permission behavior. Focus on granting equivalent API rights to Shibboleth group members while accounting for users removed from a federation whose tokens remain valid. Done means the requested access behavior is implemented and verified against those membership and token cases.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.