gravitational/teleport · error
proto: wrong wireType = %d for field SubKind
Error message
proto: wrong wireType = %d for field SubKind
What it means
Protobuf unmarshal guard in generated code for IdentityCenterAccountAssignment: the SubKind field (field 2) arrived with an unexpected wire type instead of the length-delimited type expected for a string.
Source
Thrown at api/client/proto/authservice.pb.go:60996
break
}
}
intStringLen := int(stringLen)
if intStringLen < 0 {
return ErrInvalidLengthAuthservice
}
postIndex := iNdEx + intStringLen
if postIndex < 0 {
return ErrInvalidLengthAuthservice
}
if postIndex > l {
return io.ErrUnexpectedEOF
}
m.Kind = string(dAtA[iNdEx:postIndex])
iNdEx = postIndex
case 2:
if wireType != 2 {
return fmt.Errorf("proto: wrong wireType = %d for field SubKind", wireType)
}
var stringLen uint64
for shift := uint(0); ; shift += 7 {
if shift >= 64 {
return ErrIntOverflowAuthservice
}
if iNdEx >= l {
return io.ErrUnexpectedEOF
}
b := dAtA[iNdEx]
iNdEx++
stringLen |= uint64(b&0x7F) << shift
if b < 0x80 {
break
}
}
intStringLen := int(stringLen)
if intStringLen < 0 {View on GitHub (pinned to 1283425b60)
Solutions
- Verify sender and receiver use compatible protobuf definitions/versions of authservice
- Check for truncated or corrupted payloads and re-send the request
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at api/client/proto/authservice.pb.go:60996 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of gravitational/teleport@1283425b60 (2026-09-02).
Data as JSON: /api/errors/af44b6297938c50a.
Report an issue: GitHub.