Signing of Synapse authentication header does not correctly URL encode the URL path

Description

Original title: * More informative error for trying to create a queue that already exists in Synapse*

Debugging info here:
https://sagebionetworks.jira.com/browse/SYNPY-1093?focusedCommentId=120670&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-120670

Environment

python

Activity

Show:
Ziming Dong
September 15, 2020, 7:58 PM
Bruce Hoff
March 17, 2020, 10:45 PM

Amazing! This issue first arose four years earlier: https://sagebionetworks.jira.com/browse/SYNPY-30

Bruce Hoff
March 17, 2020, 10:02 PM

Updating the title

Thomas Yu
March 17, 2020, 9:59 PM
Edited

I think the issue is that the python client catches the 409 error that is thrown and tries to update the evaluation queue which causes this invalid signature issue:

Bruce Hoff
March 17, 2020, 9:32 PM

We do not return "Invalid digital signature" when a name is already used. This error is returned when the client has not correctly authenticated. This error will happen if the API key on the client machine is wrong.

Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Jordan Kiang

Reporter

Thomas Yu

Labels

Validator

Thomas Yu