Ian Costanzo
Ian Costanzo
pyld is not correctly loading json-ld content from https://schema.org, when http://schema.org is used in the context. There are two open PR's that fix this issue (https://github.com/digitalbazaar/pyld/pull/129 and https://github.com/digitalbazaar/pyld/pull/141). It would...
Addresses issue https://github.com/hyperledger/aries-cloudagent-python/issues/1868
Add a second endpoint to retrieve the sub-wallet's bearer token, which requires both `wallet_id` and `wallet_key` to be provided. Update the existing endpoint `GET /multitenancy/wallet//token` to remove the optional `wallet_key`...
indy-sdk has some support for reading arbitrary ledger transactions, see: https://github.com/hyperledger/indy-sdk/blob/master/libindy/src/api/ledger.rs aca-py uses some of these functions internally but doesn't expose any of them through its api would probably be...
Currently there's no way to "refuse" a connection and send a message to the other party. The mechanism to use is problem reports but there's no "problem-report" endpoint for connections...
This is dependant on persistent queues (PR https://github.com/hyperledger/aries-cloudagent-python/pull/1604) and giving aca-py the ability to "hold" inbound messages until the unmanaged wallet can be activated. See the original multitenancy design: https://hackmd.io/Rpx9CahTRJKtPAJxxqqYRQ
Add a persistence mechanism to the event queue. Currently events are stored in an in-memory queue, which is lost if the agent re-starts, and is not available between agent instances...
Currently OOB invitation is generated as: {'invitation': {'@id': 'bc978133-5841-4de7-a221-64300a6282ab', '@type': 'https://didcomm.org/out-of-band/1.0/invitation', 'label': 'Bob', 'handshake_protocols': ['https://didcomm.org/didexchange/1.0'], 'request~attach': None, 'service': [{'id': '69b7d78d-a9d9-427b-b156-00e576a96027', 'type': 'did-communication', 'recipientKeys': ['did:key:z6Mkt1g9UBrtzsgrtoCqVJkuxKNnJX5diS16wxLgUdRRbTrL'], 'serviceEndpoint': 'http://192.168.65.3:9031'}]}} ... however the "service"...
Discussion points from the Aires call today (April 8), for posterity: Trace decorator: - whether the agent chooses to log trace events to the given "target" should be optional, i.e....