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

Provide centralized server authentication against metadata #5615

Closed
soltanmm opened this Issue Mar 5, 2016 · 2 comments

Comments

Projects
None yet
4 participants
@soltanmm
Contributor

soltanmm commented Mar 5, 2016

There's been a request that we provide hooks for this.

@jcanizales

This comment has been minimized.

Show comment
Hide comment
@jcanizales

jcanizales Mar 6, 2016

Contributor

Can you explain briefly what does it mean? :)

Contributor

jcanizales commented Mar 6, 2016

Can you explain briefly what does it mean? :)

@soltanmm

This comment has been minimized.

Show comment
Hide comment
@soltanmm

soltanmm Mar 9, 2016

Contributor

Currently a user of gRPC Python must, per service method, write some code to accept/reject the call based on the initial metadata. Someone's requested a server-side hook to intercept requests in one place per server.

Whether or not we actually do this, I'unno.

Contributor

soltanmm commented Mar 9, 2016

Currently a user of gRPC Python must, per service method, write some code to accept/reject the call based on the initial metadata. Someone's requested a server-side hook to intercept requests in one place per server.

Whether or not we actually do this, I'unno.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment