We've been working on a PHP implementation of the DID-Resolver and JWT signature verification components in support of a wordpress login integration. I had previously gotten it working for legacy uPort IDs but it now seems to fail with accounts created more recently.
As an example, my old account worked fine and when I polled IPFS for the user DID document corresponding to the mnid I would receive a JSON payload containing a hex public key string.
I've recently purchased a new phone and am using the latest Android uPort app for testing now with a newly created uPort ID. When this account uses the same DID resolver (full lib here https://github.com/BlockchainInstituteChi/jwttools) the call to IPFS now fails.
Here's an example of the IPFS infura call which fails to return a DID:
Am I missing something here?
Please let me know if I can provide more information.
Please sign in to leave a comment.