Versions Compared

Old Version 1

changes.mady.by.user Technical writer (Unlicensed)

Saved on

compared with

New Version 2

changes.mady.by.user Technical writer (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

The Lequinox platform does not archive transactions for external role accounts or external personal identities as they represent another organisation.


Info
Submitting the request Sign transaction for a platform-managed user will give the transaction the status ‘Opened’ and ‘Signed’, even if the application does not call the Open transaction for a platform-managed user first.


Steps

  1. Submit a request as per the details in /wiki/spaces/LPDA510/pages/1804057Sign transaction for a platform-managed user.
  2. Lequinox platform checks if the participant of the transaction is revoked. Refer to REVOKE of /wiki/spaces/LPDA510/pages/1804140. Revoked participant cannot sign the transaction.
  3. Lequinox platform checks if the transaction can be opened and signed and is not locked. Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER of /wiki/spaces/LPDA510/pages/1804140 Service.
  4. It then signs the transaction on behalf of platform-managed user.
  5. Lequinox platform archives the signed status of the transaction along with the timestamp.
  6. /wiki/spaces/LPDA510/pages/1804753ParticipantStatusResponse is returned.


Plantuml


Error messages

Expand
title


HTTP status codeMessageComments
400Unknown error

This error is returned when

400Input not valid: Transaction can not be emptyThis error is returned when the parameter 'transaction' is missing in /wiki/spaces/LPDA510/pages/1804583in ManagedUserTransactionRequest.
400Invalid role ID formatThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrectly formatted. 
400Input not valid: Participant can not be null.This error is returned when the user parameter is not mentioned in /wiki/spaces/LPDA510/pages/1804583in ManagedUserTransactionRequest.
400

Input not valid: Participant can not be of unknown type: null

This error is returned when

  • The participant is empty.
    • The parameter 'type' is missing from User (participant).
400Input not valid: Participant corporateId can not be null for corporate or server user.
400Input not valid: Participant applicationAccessId can not be null for private or corporate user.
400Input not valid: Participant privateId can not be null for private or corporate user.
400Managed identity was not foundThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is  is incorrect.
500

An unexpected error occurred: Type definition error: [...]

An unexpected error occurred: JSON parse error: [...]

These errors are returned if one or more parameters is of the wrong type.