build: add the django-shibboleth-remoteuser fork #828

[MyPyDavid]

Description

Related issue: #828

Motivation and Context

How has this been tested?

Screenshots (if appropriate)

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

Checklist

• I have read the contributor guide.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[afuetterer]

I would add the optional dependency group shibboleth to the optional-dependencies job in CI.

Then the dependency would be installed in CI and we'll see, if
a) the dependency is "installable"
b) if there are conflicts with other optional dependencies

rdmo/.github/workflows/ci.yml

Line 139 in a54867e

- run: python -m pip install .[allauth,ci,dev,gunicorn,ldap,mysql,postgres,pytest]

[afuetterer]

Looks good to me.

Forked django-shibboleth-remoteuser is installed alright.
https://github.com/rdmorganiser/rdmo/actions/runs/6979630741/job/18993276758#step:7:42

[afuetterer]

We talked about this dependency last time, right?

The original repo now has a version 0.12 avaible.
https://github.com/Brown-University-Library/django-shibboleth-remoteuser/tags

But this is another issue.

[jochenklar]

I already rebased our fork to the current upstream master.