1060490 - Investigate why the persona verifier cannot handle BrowserID validation for MSISDN

Status: VERIFIED WONTFIX

(Cloud Services Graveyard :: MobileID, defect)

Description

[Rémy Hubscher (:natim)]

When trying to validate a MSISDN assertion using PyBrowserID, the default remote verifier is failling.

    public-key algorithm unknown

Comment 1

[Chris Karlof [:ckarlof]]

At the least, it doesn't use correct verify: https://github.com/mozilla/PyBrowserID/blob/2414511a284cdd2ba9d789ce155e66ba29e3d0c1/browserid/verifiers/remote.py#L13

The correct endpoint for verifying these assertions is https://verifier.accounts.firefox.com/v2

Comment 2

[Chris Karlof [:ckarlof]]

I suspect this is related to bug 1059787.

What infrastructure is using the PyBrowserID library? I thought this was all in node.

Comment 3

[Rémy Hubscher (:natim)]

No it is not related with Bug 1059787 because this is more about MSISDN certificate than FxAccount assertions.

So can we say that PyBrowserID is wrong then and verify it manually as I did here: https://github.com/spiral-project/daybed-browserid/blob/initial_code/daybed_browserid/views.py

Comment 4

[Ryan Kelly [:rfkelly]]

Yeah, you're probably better off posting directly to the hosted verifier for this, PyBrowserID has not really been updated to account for the new FxA hosted verifier (it'll work if using it for some simple things, but there are many format/api changes that it does not support)

Comment 5

[James Bonacci [:jbonacci]]

OK.