- Had to chnage the core API to add a destroy function pointer in
grpc_auth_metadata_processor.
- Tested end to end.
- Fixed some issues in the server_auth_filter (we were not checking the
length which put us at risk of an overflow).
This is a repro case for a bug where if the client is sending
full throttle and the receiver is not able to keep up, the
client reaches a case where it doesn't make forward progress
anymore.
Signed-off-by: Craig Tiller <craig.tiller@gmail.com>
- Removing service_accounts credentials. These credentials just have
drawbacks compared to service_account_jwt_access credentials, notably
in terms for security.
- Renaming Google specific credentials with a Google prefix for C and
C++. This should be done as well for wrapped languages.
Rephrase API's such that resolvers are constrained to be able to provide a
default host given just the text of the URI channel target.
This avoids needing to rewrite such details in the core library during
retries, and generally makes things much saner to debug.
- We always do the processing asynchronously but maintain a synchronous
API for the implementor of the processor.
- there are a lot of string copies right now. Having a StringPiece
object in grpc++ would really help with that (as we would use it for
C++ metadata).
- Please review the API carefully and if you're happy with it, I'll
proceed with tests.