Skip to content

Conversation

@ST-DDT
Copy link
Collaborator

@ST-DDT ST-DDT commented Dec 11, 2018

This allows the AuthenticationManager to decide based on attributes such
as the remote or local address. For example it could decide whether the
client originates from a blacklisted ip-range. Another example could be
using multiple inbound addresses for internal and external use which use
a different set of AuthenticationProviders.

Multiple inbound addresses for netty will be added via grpc/grpc-java#5067 .

This allows the AuthenticationManager to decide based on attributes such
as the remote or local address. For example it could decide whether the
client originates from a blacklisted ip-range. Another example could be
using multiple inbound addresses for internal and external use which use
a different set of AuthenticationProviders.
@ST-DDT ST-DDT added the enhancement A feature request or improvement label Dec 11, 2018
@ST-DDT ST-DDT requested a review from yidongnan December 11, 2018 17:05
@yidongnan yidongnan merged commit 5d9f0cf into grpc-ecosystem:master Dec 14, 2018
@ST-DDT ST-DDT deleted the add-auth-userdetails branch December 14, 2018 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement A feature request or improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants