Current the next generation of the sharing server is not properly able to handle authorization tokens. These are part of the delta sharing spec. While we want to enable adopters to inject their own token management, we need to provide some basics to run a secured server.
Once we do this it would of course be great to also support #46 to not expose tokens to the whole world.
Solution
Provide basic abstractions and implementations to handle tokens / profiles.
Alternative solutions
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Problem description
Current the next generation of the sharing server is not properly able to handle authorization tokens. These are part of the delta sharing spec. While we want to enable adopters to inject their own token management, we need to provide some basics to run a secured server.
Once we do this it would of course be great to also support #46 to not expose tokens to the whole world.
Solution
Provide basic abstractions and implementations to handle tokens / profiles.
Alternative solutions
No response
Code of Conduct