fmgp.did.comm.protocol.reportproblem2
Members list
Type members
Classlikes
DID is unusable. - A DID is unusable because its method is unsupported — or because its DID doc cannot be parsed — or because its DID doc lacks required data.
DID is unusable. - A DID is unusable because its method is unsupported — or because its DID doc cannot be parsed — or because its DID doc lacks required data.
Attributes
- Supertypes
- Self type
-
CD_did.type
Failed for legal reasons.
Failed for legal reasons.
An injunction or a regulatory requirement prevents progress on the workflow. Compare HTTP status code 451.
Attributes
- Supertypes
- Self type
-
CD_legal.type
Internal error.
Internal error.
The problem is with conditions inside the problem sender’s system. For example, the sender is too busy to do the work entailed by the next step in the active protocol. Problems in this category resemble HTTP’s 5xx status codes.
Attributes
- Supertypes
- Self type
-
CD_me.type
A required resource is inadequate or unavailable. - The following subdescriptors are also defined: me.res.net, me.res.memory, me.res.storage, me.res.compute, me.res.money
A required resource is inadequate or unavailable. - The following subdescriptors are also defined: me.res.net, me.res.memory, me.res.storage, me.res.compute, me.res.money
Attributes
- Supertypes
- Self type
-
CD_me_res.type
Bad message.
Bad message.
Something is wrong with content as seen by application-level protocols (i.e., in a plaintext message). For example, the message might lack a required field, use an unsupported version, or hold data with logical contradictions. Problems in this category resemble HTTP’s 400 status code.
Attributes
- Supertypes
- Self type
-
CD_msg.type
Circumstances don’t satisfy requirements.
Circumstances don’t satisfy requirements.
A behavior occurred out of order or without satisfying certain preconditions — or circumstances changed in a way that violates constraints. For example, a protocol that books plane tickets fails because, halfway through, it is discovered that all tickets on the flight have been sold.
Attributes
- Supertypes
- Self type
-
CD_req.type
Failed to satisfy timing constraints.
Failed to satisfy timing constraints.
A message has expired — or a protocol has timed out — or it is the wrong time of day/day of week.
Attributes
- Supertypes
- Self type
-
CD_req_time.type
Attributes
- Supertypes
-
class Objecttrait Matchableclass Any
- Known subtypes
-
object CD_tust_.typeobject CD_tust_crypto_.type
Failed to achieve required trust.
Failed to achieve required trust.
Typically this code indicates incorrect or suboptimal behavior by the sender of a previous message in a protocol. For example, a protocol required a known sender but a message arrived anoncrypted instead — or the encryption is well formed and usable, but is considered weak. Problems with this descriptor are similar to those reported by HTTP’s 401, 403, or 407 status codes.
Attributes
- Supertypes
- Self type
-
CD_tust_.type
Cryptographic operation failed.
Cryptographic operation failed.
A cryptographic operation cannot be performed, or it gives results that indicate tampering or incorrectness. For example, a key is invalid — or the key types used by another party are not supported — or a signature doesn’t verify — or a message won’t decrypt with the specified key.
Attributes
- Supertypes
- Self type
-
CD_tust_crypto_.type
Unable to transport data.
Unable to transport data.
The problem is with the mechanics of moving messages or associated data over a transport. For example, the sender failed to download an external attachment — or attempted to contact an endpoint, but found nobody listening on the specified port.
Attributes
- Supertypes
- Self type
-
CD_xfer.type
https://identity.foundation/didcomm-messaging/spec/#problem-reports
Value parameters
- scope
-
gives the sender’s opinion about how much context should be undone if the problem is deemed an erro.
pif error undo the full protocolmif error undo last step-
if error until state
- sorter
-
tells whether the consequence of the problem are fully understood.
eis a errorwis a warning
Attributes
- Companion
- object
- Supertypes
Attributes
- Companion
- class
- Supertypes
-
trait Producttrait Mirrorclass Objecttrait Matchableclass Any
- Self type
-
ProblemCode.type
{
"type": "https://didcomm.org/report-problem/2.0/problem-report",
"id": "7c9de639-c51c-4d60-ab95-103fa613c805",
"pthid": "1e513ad4-48c9-444e-9e7e-5b8b45c5e325",
"ack": ["1e513ad4-48c9-444e-9e7e-5b8b45c5e325"],
"body": {
"code": "e.p.xfer.cant-use-endpoint",
"comment": "Unable to use the {1} endpoint for {2}.",
"args": [
"https://agents.r.us/inbox",
"did:sov:C805sNYhMrjHiqZDTUASHg"
],
"escalate_to": "mailto:admin@foo.org"
}
}
Value parameters
- ack
-
OPTIONAL - It SHOULD be included if the problem in question was triggered directly by a preceding message. (Contrast problems arising from a timeout or a user deciding to cancel a transaction, which can arise independent of a preceding message. In such cases, ack MAY still be used, but there is no strong recommendation.)
- args
-
OPTIONAL - Contains situation-specific values that are interpolated into the value of comment, providing extra detail for human readers. Each unique problem code has a definition for the args it takes. In this example, e.p.xfer.cant-use-endpoint apparently expects two values in args: the first is a URL and the second is a DID. Missing or null args MUST be replaced with a question mark character (?) during interpolation; extra args MUST be appended to the main text as comma-separated values.
- code
-
REQUIRED - Deserves a rich explanation; see Problem Codes below.
- comment
-
OPTIONAL - but recommended. Contains human-friendly text describing the problem. If the field is present, the text MUST be statically associated with code, meaning that each time circumstances trigger a problem with the same code, the value of comment will be the same. This enables localization and cached lookups, and it has some cybersecurity benefits. The value of comment supports simple interpolation with args (see next), where args are referenced as {1}, {2}, and so forth.
- escalate_to
-
OPTIONAL - Provides a URI where additional help on the issue can be received.
- pthid
-
REQUIRED - The value is the thid of the thread in which the problem occurred. (Thus, the problem report begins a new child thread, of which the triggering context is the parent. The parent context can react immediately to the problem, or can suspend progress while troubleshooting occurs.)
Attributes
- Companion
- object
- Supertypes
Attributes
- Companion
- class
- Supertypes
-
trait Producttrait Mirrorclass Objecttrait Matchableclass Any
- Self type
-
ProblemReport.type