-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add RFC-002: CORS and authn for Go #123
Conversation
Add an RFC for creating CORS and authentication packages for users of Connect in Go.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I've added the current maintainers of the various Connect implementations as reviewers. I'm formally in favor of adding these small quality-of-life packages to the Connect project. Formally approving this RFC requires approval from an additional 5 maintainers (since we have a total of 10). Maintainers, please indicate support or opposition using Github's code review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, these make sense to me as something to provide as first class support. They are pretty common patterns by most applications. I think having these too will help guide users of Connect on the patterns for implementing more custom things that fall outside of interceptors too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very excited to have both of these packages available!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Providing a source of truth for CORS setup, and a standardized mechanism for propagating identity, are both great additions in my book.
👍 for adding the features as separate modules. This should keep connect-go as slim and flexible as possible.
Add the plumbing required to resolve the connectrpc.com/authn and connectrpc.com/cors import paths (proposed and approved in #123).
Add an RFC for creating CORS and authentication packages for users of
Connect in Go.