Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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


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

Steps

  1. Submit a request in accordance with the details in Sign transaction as a platform-managed user.
  2. The 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. The platform checks if the transaction can be opened and signed and is not locked. Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER of Service.
  4. It then signs the transaction on behalf of platform-managed user.
  5. The  platform archives the signed status of the transaction along with the timestamp.
  6. ParticipantStatusResponse is returned.


Error rendering macro 'plantuml' : Page loading failed

Error messages

 
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 ManagedUserTransactionRequest.
400Invalid role ID formatThe parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is not in the correct format. 
400Input not valid: Participant can not be null.This error is returned when the user parameter is not mentioned in 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 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.



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


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

Steps

  1. Submit a request in accordance with the details in Sign transaction as a platform-managed user.
  2. The 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. The platform checks if the transaction can be opened and signed and is not locked. Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER of Service.
  4. It then signs the transaction on behalf of platform-managed user.
  5. The platform archives the signed status of the transaction along with the timestamp.
  6. ParticipantStatusResponse is returned.


Error messages

 
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 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 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 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.



  • No labels