Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing access rights for Seed Objects to Stanford Only #46

Open
edsu opened this issue Jun 20, 2022 · 1 comment
Open

Changing access rights for Seed Objects to Stanford Only #46

edsu opened this issue Jun 20, 2022 · 1 comment
Labels
needs analysis cannot proceed with this issue without analysis web archiving 2022 web archiving work cycle

Comments

@edsu
Copy link
Contributor

edsu commented Jun 20, 2022

In Argo users can set the access rights of a Seed Object to Stanford Only, which ideally should make the website URL only available to people who are on campus, or logged into the VPN.

pywb's Access Controls should allow the ACLJ file to limit access based on the presence of a X-Pywb-ACL-User HTTP header. For example if this header was set to Stanford then an ACLJ rule could be written to indicate that a given URL should only be available to the Stanford user.

It seems like this header could be conditionally set in the Apache configuration based on another HTTP header that is sent upstream by Stanford's Single Sign On Proxy? For example what does Stacks do to control this type of access? We need to do some analysis to see if this is possible. If it is possible then we need to also modify the daemon created as part of #10 to modify the ACLJ for Stanford Only rights changes as well.

@edsu edsu added web archiving 2022 web archiving work cycle needs analysis cannot proceed with this issue without analysis labels Jun 20, 2022
@lwrubel
Copy link
Contributor

lwrubel commented Jul 25, 2022

Iceboxing since there is not a pywb API (yet, at least) for handling this and not wanting to add complexity with a daemon as described in #10, which is Iceboxed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs analysis cannot proceed with this issue without analysis web archiving 2022 web archiving work cycle
Projects
None yet
Development

No branches or pull requests

2 participants