Integrate enmeshed

If you wish to share one of your OwnIdentityAttributes with a peer, this use case allows you to do so. Internally, a Request with a ShareAttributeRequestItem will be created and will be sent via Message to the peer. Assuming your peer accepts the Request, at their side a PeerIdentityAttribute will be created. The corresponding Response informs you about their acceptance and creates AttributeForwardingDetails associated with the OwnIdentityAttribute.

Please note further, that this use case is meant to be used to share a version of an OwnIdentityAttribute for the first time. If you have already shared another version of a succeeded Attribute with the peer and you want to let them know about the changes to its value, use the Notify peer about OwnIdentityAttribute succession use case.

Parameters

  • The attributeId of your OwnIdentityAttribute.
  • The address of the peer.
  • Optionally requestMetadata as described in the data model, except for the id and items, which are handled automatically.

On Success

  • The LocalRequest is returned, that is associated with the Request which was sent to the peer.

On Failure

  • The Request cannot be created if the peer is unknown.
  • The Request cannot be created if the attributeId doesn’t belong to an OwnIdentityAttribute.
  • The Request cannot be created if the OwnIdentityAttribute has already been shared with the peer and it doesn’t have "DeletedByRecipient" or "ToBeDeletedByRecipient" as deletionInfo.deletionStatus.
  • The Request cannot be created if another version of the OwnIdentityAttribute regarding succession has already been shared with the peer, unless the latest shared version has "DeletedByRecipient" as deletionInfo.deletionStatus.
  • The Request cannot be created if the parameters are malformed.