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

Figure out worker-to-worker auth contexts #29

Open
nathanclevenger opened this issue Sep 27, 2022 · 5 comments
Open

Figure out worker-to-worker auth contexts #29

nathanclevenger opened this issue Sep 27, 2022 · 5 comments
Labels

Comments

@nathanclevenger
Copy link
Member

nathanclevenger commented Sep 27, 2022

Now that @AggressivelyMeows confirmed that the cf-worker header can't be spoofed for incoming traffic, we should use this for authenticating service requests. We should give it a different context, and as a non user role, we shouldn't allow certain permissions things, but this can start to allow us to require auth for many of the .do services ... even ones that have lots of dependencies

@sam-lippert
Copy link
Contributor

How should we maintain a list of zones? https://api-cf.drivly.workers.dev/zones lists all current zones and this can be imported into ctx.do, but we'll likely need to create a sync process to keep it updated. Calling the API directly probably isn't an option due to latency.

@nathanclevenger
Copy link
Member Author

nathanclevenger commented Apr 14, 2023 via email

@sam-lippert sam-lippert removed the question Further information is requested label Apr 17, 2023
@sam-lippert
Copy link
Contributor

@nathanclevenger Why don't we use queues for worker-to-worker communication?

@nathanclevenger
Copy link
Member Author

@sam-lippert I think we can - but it depends on whether the use case is sync or async ... if the caller needs a response to proceed then it needs to be blocking sync, but if the communication doesn't need the result to return it's own response - then it would definitely make sense

@sam-lippert sam-lippert removed their assignment Nov 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants