authenticating non-public data access within app
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
EDIT: as it stands, the main remaining issue is that we need to fetch auth tokens from the http header within the app to prevent access to non-public data via the API url. currently, we have no data available, but one could bypass it this way.
Check API requests and remaining todos in auth.py and 1e2b4dde7240a2057ba6e0fa08bdfb7095a8cf55 @havok2063
I'm currently unable to progress any further with the version of valis I have running on the docker, as it returns 502 errors -- which I presume is because it's trying to authenticate with api.sdss.org/credentials/crown
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with auth.py and review the API requests and remaining TODOs referenced in the issue, then inspect how the Docker-running valis instance handles authentication. Done means auth tokens are obtained from the HTTP header within the app so non-public data cannot be accessed through the API URL; also verify whether the reported 502 behavior is related.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100