You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently synapse write the OAuth in the format {"data": {"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}}
But nucleus reads OAuth in the following format {"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}
What is the expected behavior?
The read and write structure of OAuth should be consistent for proper functioning of synapse
Synapse write structure should be {"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}
Steps To Reproduce
Connect synapse
Run a job (via adding commit)
The job will fail
Version
Test-at-scale Community Edition
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What is the current behavior?
Currently synapse write the OAuth in the format
{"data": {"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}}
But nucleus reads OAuth in the following format
{"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}
What is the expected behavior?
The read and write structure of OAuth should be consistent for proper functioning of synapse
Synapse write structure should be
{"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}
Steps To Reproduce
Version
Test-at-scale Community Edition
The text was updated successfully, but these errors were encountered: