package api

Get desktop application:
View/edit binary Protocol Buffers messages

Messages for authentication protocol between a sender and a receiver.

Used in: DeviceAuthMessage

(message has no fields)

Used in: DeviceAuthMessage

• required AuthError.ErrorType error_type = 1

Used in: AuthError

• INTERNAL_ERROR = 0

• NO_TLS = 1

  The underlying connection is not TLS

Used in: DeviceAuthMessage

• required bytes signature = 1

• required bytes client_auth_certificate = 2

• required CastMessage.ProtocolVersion protocol_version = 1

• required string source_id = 2

  source and destination ids identify the origin and destination of the message. They are used to route messages between endpoints that share a device-to-device channel. For messages between applications: - The sender application id is a unique identifier generated on behalf of the sender application. - The receiver id is always the the session id for the application. For messages to or from the sender or receiver platform, the special ids 'sender-0' and 'receiver-0' can be used. For messages intended for all endpoints using a given channel, the wildcard destination_id '*' can be used.

• required string destination_id = 3

• required string namespace = 4

  This is the core multiplexing key. All messages are sent on a namespace and endpoints sharing a channel listen on one or more namespaces. The namespace defines the protocol and semantics of the message.

• required CastMessage.PayloadType payload_type = 5

• optional string payload_utf8 = 6

  Depending on payload_type, exactly one of the following optional fields will always be set.

• optional bytes payload_binary = 7

What type of data do we have in this message.

Used in: CastMessage

• STRING = 0

• BINARY = 1

Always pass a version of the protocol for future compatibility requirements.

Used in: CastMessage

• CASTV2_1_0 = 0

• optional AuthChallenge challenge = 1

  Request fields

• optional AuthResponse response = 2

  Response fields

• optional AuthError error = 3