protos/pogo0.437.0

You are looking at version 0.431.0. The latest is 0.437.0. See it in 0.437.0What changed in 0.431.0

Messageholoholo.rpc

DeviceVerificationAuditRecordProto

holoholo.rpc.DeviceVerificationAuditRecordProtoFile: holo_protos.protoC# type: Com.Nianticproject.Platform.Deviceregistration.DeviceVerificationAuditRecordProto12 fieldsSince 0.431.0

No.FieldTypeTag
1audit_record_idstring0a
2user_idstring12
3device_registration_idstring1a
4challenge_idstring22
5previous_statusDeviceVerificationStatus28
6new_statusDeviceVerificationStatus30
7event_typeDeviceVerificationAuditRecordProto.EventType38
8actor_typeDeviceVerificationAuditRecordProto.ActorType40
9actor_idstring4a
10reasonstring52
11timestamp_msint6458
12request_idstring62

Nested types

Used in (0)

No message has a field of this type. That is usual for RPC requests and responses, which travel on their own.

.proto source
// holo_protos.proto · package holoholo.rpc
message DeviceVerificationAuditRecordProto {
  string audit_record_id = 1;
  string user_id = 2;
  string device_registration_id = 3;
  string challenge_id = 4;
  DeviceVerificationStatus previous_status = 5;
  DeviceVerificationStatus new_status = 6;
  EventType event_type = 7;
  ActorType actor_type = 8;
  string actor_id = 9;
  string reason = 10;
  int64 timestamp_ms = 11;
  string request_id = 12;

  enum ActorType {
    ACTOR_TYPE_UNSPECIFIED = 0;
    ACTOR_TYPE_PLAYER = 1;
    ACTOR_TYPE_PX = 2;
    ACTOR_TYPE_SYSTEM = 3;
  }

  enum EventType {
    EVENT_TYPE_UNSPECIFIED = 0;
    EVENT_TYPE_CHALLENGE_CREATED = 1;
    EVENT_TYPE_CHALLENGE_VIEWED = 2;
    EVENT_TYPE_CHALLENGE_CONFIRMED = 3;
    EVENT_TYPE_CHALLENGE_DENIED = 4;
    EVENT_TYPE_CHALLENGE_EXPIRED = 5;
    EVENT_TYPE_CHALLENGE_SUPERSEDED = 6;
    EVENT_TYPE_DEVICE_PROMOTED = 7;
    EVENT_TYPE_DEVICE_EVICTED = 8;
    EVENT_TYPE_PX_OVERRIDE = 9;
  }
}