Present proof 2

[Gavinok]

No description provided.

[cvarjao]

@loneil , what version of BC Wallet did you test with? version 1.0.18 was release yesterday

[loneil]

@cvarjao for this branch testing proof 2.0 I'm using 1.0.18 build 1801 for both Android and iOS (on the beta on Android but not iOS but looks like same release for today)

[esune]

@loneil yes, unless we have a good reason to drop conenction-less right away we should maintain support for now. We'll plan to slowly move away from it though.

[cvarjao]

When trying to receive an OOB invite from aca-py via Credo I get some error message in Credo about DID Rotate attachment is missing.

[jamshale]

When trying to receive an OOB invite from aca-py via Credo I get some error message in Credo about DID Rotate attachment is missing.

This issue came up a little while ago but I thought it had been addressed from the aca-py side and closed the issue openwallet-foundation/acapy#3020.

[cvarjao]

So, what would be the correct API call for using did:peer:4?
I've tried using:

http.post(`/out-of-band/create-invitation`,{
            "accept":["didcomm/aip1","didcomm/aip2;env=rfc19"],
            "alias":`Faber\`s 😇 - ${new Date().getTime()}`,
            "goal":"",
            "goal_code":"",
            "handshake_protocols":["https://didcomm.org/didexchange/1.0"],
            "my_label":`Faber\`s 😇 - ${new Date().getTime()}`,
            "protocol_version":"1.1",
            "use_public_did":false,
            "use_did_method": "did:peer:4",
        }, {
            params: {
                "auto_accept": true,
                "multi_use": false,
                "create_unique_did": false,
            },
            headers:{
                'Content-Type': 'application/json',
                'Authorization': `Bearer ${config.auth_token}`
            }
        })

[esune]

So, what would be the correct API call for using did:peer:4? I've tried using:

http.post(`/out-of-band/create-invitation`,{
            "accept":["didcomm/aip1","didcomm/aip2;env=rfc19"],
            "alias":`Faber\`s 😇 - ${new Date().getTime()}`,
            "goal":"",
            "goal_code":"",
            "handshake_protocols":["https://didcomm.org/didexchange/1.0"],
            "my_label":`Faber\`s 😇 - ${new Date().getTime()}`,
            "protocol_version":"1.1",
            "use_public_did":false,
            "use_did_method": "did:peer:4",
        }, {
            params: {
                "auto_accept": true,
                "multi_use": false,
                "create_unique_did": false,
            },
            headers:{
                'Content-Type': 'application/json',
                'Authorization': `Bearer ${config.auth_token}`
            }
        })

Might be best to ask in the ACA-Py Discord or repo rather than in this PR, as this is ACA-Py behaviour (not specific to VC-AuthN).
That being said, i think what you are doing is right: https://aca-py.org/latest/features/QualifiedDIDs/#context

[jamshale]

Just FYI, I think that payload looks correct. If it's not working then I'm not sure why.

[Gavinok]

As Lucas mentioned the body of the attachments are already base64 encoded so I figured we could remove the use of the build method and simply unpack the contents and add the new format field. This should now work with connectionless

[esune]

I am able to scan the QR code in BC Wallet and respond to the proof-request (which is happening QUITE quickly), but then the page in the demo app does not update to the success state and navigate away.

[esune]

I am able to scan the QR code in BC Wallet and respond to the proof-request (which is happening QUITE quickly), but then the page in the demo app does not update to the success state and navigate away.

Nevermind, the issue was with me using a CANdy prod credential to respond at the proof, and that ledger not being in the agent config. Everything works as expected.

[esune]

LGTM 👍🏻

[loneil]

Tested out the config permutations locally, working for me. The connectionless proof is working now after the attachment change
Just minor change now that we can update to the latest RC of 1.0.0