Is it possible to change Notary Signers?

Hi Ryan, The short answer for this is No. In a transaction with notary exists, other signers besides notary can be reassignable while notary can't. And this will be validated when you send the package so there's basically no workaround for this. And also, Group Recipients cannot be contained in a notarized transaction, so Group Feature also won't work in this case. Duo

Duo, I believe we were told earlier that this was possible by removing the notary and all associated notary fields. Then we could add them back in with the new notary information and all would be set. Any truth to that one?

Hi Ryan, I think what you mean is, to reassign notary manually by code instead of using this "reassign" feature. So I think you will have to control the "change notary" flow at your own side. If in that case, I think it could be possible. I would have a quick test and tell you the result ASAP. Duo

Yes, that is basically what I am talking about. We'd use the REST API to make the changes. Let me know what you get based off of your changes.

Hi Ryan, I just had a quick test, on top of the workflow we discussed before, you can add these steps in the middle: (1)when you want to change a notary, change your package status to "DRAFT" and remove your notary role id like this: "notaryRoleId": null (in two separate calls) (2)call the update role function like below, the PUT request would override everything in the original role and OSS would recognize your notary profile automatically, so you just need to assign these necessities as the payload example shows.

HTTP Request
PUT /api/packages/{packageId}/roles/{roleId}

HTTP Headers
Accept: application/json
Content-Type: application/json
Authorization: Basic api_key

Request Payload
  {
         "id":"role_notary",
         "type":"SIGNER",
         "signers":[
            {   
               "email":"[email protected]",   
            }
         ],
         "name":"role_notary"
      }

(3)assign your notary role id and sent the package. (in two separate calls)

Duo, I am going through the steps that we've discussed and I am getting the following error when I try to update the package with a new notary. { "messageKey": "error.internal.default", "message": "Unexpected error. We apologize for any inconvenience this may have caused you, please try again. If the problem persists, please contact our support team.", "code": 500, "name": "Unhandled Server Error" } Is there any way to figure out exactly what is going on or what I am doing wrong so I can move past this step?

Hi Ryan, For a better troubleshooting purpose, we suggest to use HTTP monitor tools like Fiddler monitoring the traffic going to OSS. With Fiddler, you can find out which API call returns a 500 and then it's easier for us to analyze what may be wrong in the code or in the process itself. Duo