Push Scicat authentication from client to backend service?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 4
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 40
Description
The data reduction service will need to load files from Scicat with Scitacean. While some of these files (calibration, vanadium, ...) might be available with instrument-wide permissions (and could therefore be more static), another case is runs of the current experiment, such as transmission runs or background runs, which would require Beamlime to authenticate as the current user.
As far as I understand Nicos may have the authentication token and might be able to push it to the Beamlime service?
@jl-wynen @hurvan
Contributor guide
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 by clarifying how Scicat authentication should move between Nicos, Beamlime, and the data reduction service, including the Scitacean access needed for experiment runs. The issue names no files or tests; done would be an agreed implementation scope and authentication flow for the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100