Task #153
closed
Determine how to add additional content protection
Status:
CLOSED - DUPLICATE
Description
In addition to our normal repo_auth WSGIAccessScript, some deployments need to do additional custom authorization. This task is to determine what the best way is to facilitate that. Ideally, we will be able to use apache to specify multiple methods.
That's an option, although on first glance, it looks like the existing plugin system requires the upstream auth script to know about optional plugins in advance. It would be much better to allow arbitrary plugins to be added to a deployment. Ideally we'd be able to let apache handle this.
- Tags Sprint Candidate added
- Sprint/Milestone set to 12
- Status changed from NEW to ASSIGNED
- Assignee set to cduryee
- Status changed from ASSIGNED to POST
I emailed a few folks to get feedback for an idea for this. I will create a new task with details once I get feedback.
- Status changed from POST to 7
- Tags deleted (
Sprint Candidate)
- Is duplicate of Story #720: As a pulp administrator, I would like to enable a custom auth check for content downloads added
- Status changed from 7 to CLOSED - DUPLICATE
- Sprint set to February 2015
- Sprint/Milestone deleted (
12)
Also available in: Atom
PDF
.