gRPC 7 PERMISSION_DENIED vs 13 INTERNAL
Both gRPC 7 (PERMISSION_DENIED) and 13 (INTERNAL) belong to the gRPC Status Codes category. 7 indicates that the caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead. Meanwhile, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.
描述
The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
何时出现
The authenticated user lacks the required role, scope, or policy to perform this action. Different from UNAUTHENTICATED (code 16), which means no credentials at all.
如何修复
Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.
描述
An internal error occurred. This means that some invariant expected by the underlying system has been broken.
何时出现
A server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
如何修复
Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.
主要区别
gRPC 7: The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.
You encounter 7 when the authenticated user lacks the required role, scope, or policy to perform this action. Different from UNAUTHENTICATED (code 16), which means no credentials at all.
You encounter 13 when a server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
何时使用哪个
For 7 (PERMISSION_DENIED): Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side. For 13 (INTERNAL): Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.