gravitational/teleport · error

proto: IdentityCenterAccountAssignment: wiretype end group f

Error message

proto: IdentityCenterAccountAssignment: wiretype end group for non-group

What it means

Protobuf unmarshal guard in generated code for IdentityCenterAccountAssignment: an end-group (wire type 4) marker was encountered without a matching start-group, meaning the message bytes are malformed. Indicates corrupt or incompatible serialized data.

Source

Thrown at api/client/proto/authservice.pb.go:60956

		var wire uint64
		for shift := uint(0); ; shift += 7 {
			if shift >= 64 {
				return ErrIntOverflowAuthservice
			}
			if iNdEx >= l {
				return io.ErrUnexpectedEOF
			}
			b := dAtA[iNdEx]
			iNdEx++
			wire |= uint64(b&0x7F) << shift
			if b < 0x80 {
				break
			}
		}
		fieldNum := int32(wire >> 3)
		wireType := int(wire & 0x7)
		if wireType == 4 {
			return fmt.Errorf("proto: IdentityCenterAccountAssignment: wiretype end group for non-group")
		}
		if fieldNum <= 0 {
			return fmt.Errorf("proto: IdentityCenterAccountAssignment: illegal tag %d (wire type %d)", fieldNum, wire)
		}
		switch fieldNum {
		case 1:
			if wireType != 2 {
				return fmt.Errorf("proto: wrong wireType = %d for field Kind", wireType)
			}
			var stringLen uint64
			for shift := uint(0); ; shift += 7 {
				if shift >= 64 {
					return ErrIntOverflowAuthservice
				}
				if iNdEx >= l {
					return io.ErrUnexpectedEOF
				}
				b := dAtA[iNdEx]

View on GitHub (pinned to 1283425b60)

Solutions

1. Verify sender and receiver use compatible protobuf definitions/versions of authservice
2. Check for truncated or corrupted payloads and re-send the request

When it happens

Trigger: Thrown at api/client/proto/authservice.pb.go:60956 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/aff151f05cf2fe86. Report an issue: GitHub.