I've been playing with the jolocom-cli and running into some errors. I've submitted two issues at jolocom/jolocom-cli#19 & jolocom/jolocom-cli#20. Who should be the best person to chat with?
HI @mnzaki , I have submitted one more issue at jolocom/jolocom-cli#21. Can you please take a look at it
3 replies
?
I am trying to setup a complete stack with the bare minimum I need to use jolocom with Smilo blockchain
I cloned the jolo-did-method, compiled it all, configured the truffle to deploy the smart contract to the smilo blockchain
then I cloned a old repo, demo-sso and now I am facing a issue that seems to be related to this
registry.authenticate(vaultedKeyProvider, {derivationPath: JolocomLib.KeyTypes.jolocomIdentityKey, encryptionPass: password})
.then(identityWallet => {
configureRoutes(app, {setAsync, getAsync, delAsync}, identityWallet, password)
configureSockets(server, identityWallet, password, new DbWatcher(getAsync), {getAsync, setAsync, delAsync})
})
it throws:
Demo service started, listening on port 9010
(node:329398) UnhandledPromiseRejectionWarning: Error: Could not retrieve DID Document. Returned error: project ID is required
at JolocomRegistry.resolve (/opt/js/jolocom/demo-sso/node_modules/jolocom-lib/ts/registries/jolocomRegistry.ts:175:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:329398) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:329398) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I think that is because I am missing
Where is your service deployed. E.g. https://demo-sso.jolocom.com
my question is, what is the service I have to have running local to pass over this err ?
is the generic backend ?
Hi @thomasmodeneis , apologies for the wait. You are correct that the generic backend would be the service to be running locally, however both Demo-SSO and the generic backend are out of date at this state. instead I would recomment to look at this dockerised example application: https://github.com/jolocom/interactions-demo
The difference is that we have moved to using our SDK for almost all services and use cases
existing work you have done to integrate your new DID method can be transferred to the SDK by implementing it similarly to the jolocom DID method here: https://github.com/jolocom/jolocom-lib/blob/next/ts/didMethods/jolo/index.ts (basically implementing the
IResolver, IRegistrar interfaces)
Hi all, I raised an issue on the jolocom generic backend, I resolved the issue. It was created because the jolocom wallet application (which i built using sdk) was generating did as did:juan:... and which were not being resolved by backend, everything worked fine with the official app on android play store. I cannot close the issue since the repo is archived.
hi @harshitg9715, the Generic Backend relies on a now-outdated version of the library. did:jun is a new DID method we have developed which works in a fully peer-to-peer way (without relying on a blockchain) and it is the new default for the smartwallet. The SDK provides built in support for both did:jun and did:jolo, however older versions of our tools do not support it. We recommend the SDK for building applications and services for this reason. A version of the wallet built on the SDK will be released publically in the coming days (already available on ios testflight and the android beta program)
could you answer what is required there so I can move forward ?
hi @chunningham , Thankyou for the clarification. The new documentation is great! I am going through the new docs now. However, it does not cover creation of public profile as of now. I was hoping if you could assist me with that. I was successful in creating an agent instance on jolo and a respective document that could be resolved on uniresolver.io.
the new impl of the jolocom DID method has a method for updating the profile. for accessing via the sdk, you can use
sdk.didMethods.get('jolo').registrar.updatePublicProfile
you will need to
// @ts-ignore that line, the .didMethods object will not show the full type
Hi @chunningham , we were able to create public profile, request and issue credentials using the generic backend but as it relies on the deprecated version of the library, we wanted to replicate the same with the new SDK but were unable to create a public profile as the docs doesnt cover this section. Can you please suggest the steps to setup an Identity with a public profile with the new SDK.
Hi @chunningham , In the creating an Identity section of the documentation, the sdk.createNewAgent method for creating agent with a new random identity does not exists in the SDK.
I assumed it must me sdk.createAgent , but upon calling this one I am getting the error: insufficient funds for intrinsic transaction cost, Is there some initial SDK configuration that I am missing ? can you please clarify this.
also, the example in the same section of docs mention loadIdentity method, which again does not exists in sdk.
Hi all, I was hoping if someone can point me in the right direction here.
some minor updates:
some minor updates:
- I was able to successfully create a public profile.
- I am unable to fetch the did of my agent on universal resolver
- I am unable to create any new agents or update the created profile again, getting INSUFFICIENT_FUNDS error.
- I even tried to fuel the registryContractAddress, but that failed as well.
you can extract the eth public key using this line:
const {publicKeyHex} = await agent.keyProvider.getPubKeyByController(password, `${keyProvider.id}#keys-2`)if you prepend 0x to publicKeyHex you have the eth address and can fuel it here: https://faucet.rinkeby.io/
Hi @chunningham , fueling did work, but i still cannot create an agent, I think there is some restrictions on infura API that is configured in the sdk. here is the new error generated by await sdk.createAgentFromMnemonic(mnemonic) :
{
reason: 'bad response',
code: 'SERVER_ERROR',
status: 403,
headers: {
date: 'Wed, 25 Nov 2020 10:16:32 GMT',
'content-type': 'application/json',
'content-length': '97',
connection: 'close',
vary: 'Origin'
},
body: '{"jsonrpc":"2.0","id":48,"error":{"code":-32002,"message":"rejected due to project ID settings"}}',
requestBody: '{"method":"eth_getTransactionReceipt","params":["0xf01c2e205f069579ae03ec16324b159c69828ac8639ab81f6972976d8fcea7f9"],"id":48,"jsonrpc":"2.0"}',
requestMethod: 'POST',
url: 'https://rinkeby.infura.io/v3/64fa85ca0b28483ea90919a83630d5d8'
}Do I need to configure my own infura API?
1 reply
Hi @chunningham , @clauxx , tried running interactions-demo based on the new SDK in my local, was able to run frontend and the service agent, one thing we couldnt understand was how do you update the web-frontend that the interaction actually succeeded like in Authentication interaction how do you make the shared credential (email) available to the web-frontend? It was apparent in generic-backend that an identifier for the JWT token was being stored as a key-value pair in the redis db along with the status of the interaction. Can you please tell how is it being done here in the interactions-demo based on the new SDK and how do you make use of the shared credentials using the new SDK because the Jolocom SDk docs doesnt cover it.
3 replies
Hi @mnzaki, we are looking into a usecase of pushing the credential to the wallet instead of asking the user to scan again to receive a credential to make it as straight forward as possible. The flow is => user scans a qr code at the login and shares his self-signed email which will be verified by an OTP , on a successfull OTP verification we want to push a signed credential to the wallet instead of asking user to scan another qr code to receive that credential. We are already using websockets with server and webclient. Is it configurable at the Wallet side to have a websocket connection with the server, so that the server can push the credential to the walllet ? . We understand it could raise potential security issues but please suggest us how we can approach this usecase. Thanks!
2 replies