appsync receiving auth errors from sauropod

RESOLVED INVALID

Status

RESOLVED INVALID
7 years ago
a month ago

People

(Reporter: rfkelly, Unassigned)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
AppSync is currently receiving authentication errors from the sauropod backend.  We believe this is due to sauropod not handling the new-style browserid assertion format, and are working on a fix inside sauropod:

  https://github.com/mozilla/sauropod/pull/25

This bug is to make sure that it doesn't get forgotten, and for us to confirm it's working from the appsync end once sauropod has been fixed.
(Reporter)

Comment 1

7 years ago
Created attachment 592027 [details] [diff] [review]
patch to update appsync to latest version of PyVEP

It turns out that the appsync code itself also has a dependency on the old BrowserID assertion format.  Attached patch updates it to use the latest PyVEP (also available as a pull request at https://github.com/mozilla/appsync/pull/7)
Attachment #592027 - Flags: review?(tarek)
(Reporter)

Comment 2

7 years ago
I have now updated the live sauropod instance to support the new assertion format.  In conjunction with the above patch, this will hopefully fix the issues...
All fixes are deployed, and it's working for me again.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Attachment #592027 - Flags: review?(tarek) → review+
The old app sync codebase is no longer going to be supported. All resolved fixed bugs are being marked as invalid, as they no longer apply to the new apps in the cloud service.
Resolution: FIXED → INVALID

Updated

a month ago
Product: Web Apps → Web Apps Graveyard
You need to log in before you can comment on or make changes to this bug.