gRPC 3 INVALID_ARGUMENT vs 7 PERMISSION_DENIED
Both gRPC 3 (INVALID_ARGUMENT) and 7 (PERMISSION_DENIED) belong to the gRPC Status Codes category. 3 indicates that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system. Meanwhile, 7 means that the caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
説明
The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
このコードが表示される場合
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
解決方法
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
説明
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.
主な違い
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 7: The caller does not have permission to execute the specified operation. This is not for unauthenticated callers — use UNAUTHENTICATED instead.
You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
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.
どちらをいつ使うか
For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 7 (PERMISSION_DENIED): Verify the caller has the correct IAM role, API scope, or access policy. Check RBAC configuration on the server side.