[BUG] verification of ES256K-R fails when verificationMethod uses checksumAddress in blockchainAccountId

[mirceanis]

Current Behavior

Here is an example test case:

  import { getAddress } from "@ethersproject/address"

  // ...

  it('handles ES256K-R algorithm with checksum address in blockchainAccountId', async () => {
    expect.assertions(1)
    const verificationMethod = {
      id: `${did}#keys-1`,
      type: 'EcdsaSecp256k1RecoveryMethod2020',
      owner: did,
      blockchainAccountId: `eip155:1:${getAddress(address)}`, // use checksum address (mixed case)
    }
    const ethResolver = {
      resolve: jest.fn().mockReturnValue({
        didDocument: {
          id: did,
          verificationMethod: [ verificationMethod ],
        },
      }),
    }
    const jwt = await createJWT({ hello: 'world' }, { issuer: aud, signer: recoverySigner, alg: 'ES256K-R' })
    const result = await verifyJWT(jwt, { resolver: ethResolver })
    return expect(result.signer).toEqual(verificationMethod)
  })

Expected Behavior

The test should pass

Failure Information

The test from above fails with invalid signature for JWT

The failure is likely caused by a case comparison of strings

[uport-automation-bot]

🎉 This issue has been resolved in version 6.1.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀