package org.signal.chat.challenge

Get desktop application:
View/edit binary Protocol Buffers messages

rpc AnswerChallenge (AnswerChallengeRequest, AnswerChallengeResponse)
challenge.proto:26
Submit proof of a challenge completion. Some server endpoints (the "send message" endpoint, for example) may return a response indicating the client must complete a challenge before continuing. Clients may use this endpoint to provide proof of a completed challenge. If successful, the client may then continue their original operation.
message AnswerChallengeRequest
challenge.proto:54
- string token = 1
  The opaque token id from the ChallengeRequired response returned by the server endpoint that requested the challenge
- oneof request
  - AnswerChallengeRequest.AnswerPushChallengeRequest push = 2
  - AnswerChallengeRequest.AnswerCaptchaChallengeRequest captcha = 3
message AnswerChallengeResponse
challenge.proto:77
- bool success = 1
  Whether the challenge proof was accepted
rpc RequestPushChallenge (RequestPushChallengeRequest, RequestPushChallengeResponse)
challenge.proto:51
Requests that a challenge value be sent to the authenticated account's primary device via push notification. Once received, callers may present the challenge value via the HandleChallengeResponse RPC. APNs challenge payloads will be formatted as follows: ``` { "aps": { "sound": "default", "alert": { "loc-key": "APN_Message" } }, "rateLimitChallenge": "{CHALLENGE_TOKEN}" } ``` FCM challenge payloads will be formatted as follows: ``` {"rateLimitChallenge": "{CHALLENGE_TOKEN}"} ```
message RequestPushChallengeRequest
challenge.proto:82
(message has no fields)
message RequestPushChallengeResponse
challenge.proto:85
- oneof response
  - google.protobuf.Empty sent_push_challenge = 1
    The server attempted to send a challenge value to the authenticated account's primary device via a push notification.
  - errors.FailedPrecondition no_push_token = 2
    The authenticated account's primary device does not have a push token.