gRPC 0 OK vs 16 UNAUTHENTICATED
Both gRPC 0 (OK) and 16 (UNAUTHENTICATED) belong to the gRPC Status Codes category. 0 indicates that the operation completed successfully. Not an error; returned on success. Meanwhile, 16 means that the request does not have valid authentication credentials for the operation.
설명
The operation completed successfully. Not an error; returned on success.
이 코드를 보게 되는 경우
The RPC completed without any issues. This is the expected response for every successful gRPC call.
해결 방법
No fix needed — this indicates everything worked correctly.
설명
The request does not have valid authentication credentials for the operation.
이 코드를 보게 되는 경우
No credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
해결 방법
Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).
주요 차이점
gRPC 0: The operation completed successfully. Not an error; returned on success.
gRPC 16: The request does not have valid authentication credentials for the operation.
You encounter 0 when the RPC completed without any issues. This is the expected response for every successful gRPC call.
You encounter 16 when no credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
언제 어떤 것을 사용할지
For 0 (OK): No fix needed — this indicates everything worked correctly. For 16 (UNAUTHENTICATED): Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).