-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement NFC support query in Service Agent #49
Comments
I think it would be nice to have a way to configure the Service Agent in a way that it will automatically request for a number of features (meaning by that protocols, capabilities, constraints, etc.) once a connection with another DIDComm agent is established. Somewhere in the configuration of Service Agent (e.g. a configuration file) we can have:
So once a connection is completed, it will automatically call: await agent.discovery.queryFeatures({connectionId, protocolVersion: 'v2', queries: [{featureType: 'capability', match: 'mrtd.*'}] }) And, upon the disclosure by the other party, it will keep track of these features by adding them to connection record, which in the simplest case would be the
In the case of the NestJS client, we can store this into the Connection entity metadata. But we will need to send an event somehow from the main Service Agent in order for it to be able to process it. Probably, a simple idea would be to add a |
Note the implementation in Hologram, which can serve as an inspiration for this: https://github.com/2060-io/hologram-app/blob/282e6275d1d4a0fb7e9e9f7220bb4ed2e9da5cb7/src/hooks/agent/connections/manageAgentConnectionEvents.ts#L8 |
This issue was created from the need we have in UnicID to know if a certain user is using a phone capable of NFC tag reading. However, we can make it more generic in order to support other use cases in the future.
NFC support can be retrieved by asking the DIDComm agent for
mrtd.emrtd-read-support
capability (to be more precise, a feature with typecapability
, namemrtd.emrtd-read-support
and valuetrue
). This is done through the Discover Features protocol.The text was updated successfully, but these errors were encountered: