Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    chunningham
    @chunningham

    Hi @iwTGBs, this is caused by that branch using an older version of the library which uses a since-deprecated Infura API. To solve, I would recommend either using the master branch of the generic backend or upgrading your jolocom-lib dependency to 4.0.1. The master branch should still work for the swimming pool as long as you keep the same config.ts file, however some type definitions may have changed slightly, e.g.:

    /* Credentials required during authentication */
    export const currentCredentialRequirements = ['a-kaart']
    
    export const credentialRequirements = {
      'a-kaart': {
        metadata: demoClaimsMetadata.akaart
      }
    } as { [key: string]: ICredentialReqSection }
    
    /* Credentials offered by the service. */
    export const credentialOffers = {} as {
      [key: string]: {
        schema: BaseMetadata
        metadata: {
          renderInfo?: CredentialOfferRenderInfo
          metadata?: CredentialOfferMetadata
        }
      }
    }

    The main changes on the aKaartIntegration branch are related to integration with an external service via adding custom middleware, so it is still a good example of that.

    Johannes
    @iwTGBs
    @chunningham i stayed on the akaart branch and updated the dependency to 4.0.1 keeping the config.ts as follows(in first snippet) and changing specified area to your new code example. He cant find CredentialOfferRenderInfo and CredentialOfferMetadata thus "yarn build " throws 8 errors.
    image.png
    Mina Nagy Zaki
    @mnzaki
    @iwTGBs that branch is really old, trust us on this one :D it's something for an old demo, and some things have changed since.
    I think a more plausible solution would be to merge master into into it to get it up to date, if you really insist on using it
    though a much better solution is as @chunningham outlined in https://gitter.im/jolocom/SmartWallet?at=5e56488cd7bb4e179ca1b614
    Johannes
    @iwTGBs
    where do i find more documentation on how the backend is connected to qr code implementation / functionality?
    Johannes
    @iwTGBs
    and/or could i get your avalon related backend configuration e.g. "config.ts" to understand it or the whole backend .tar file ;-P?
    agruener2000
    @agruener2000
    Hi, on which Ethereum network is Jolocom connecting and creating the identities?
    Johannes
    @iwTGBs
    @mnzaki after the wallet sends the POST request and the data the frontend requested to the backend, does the backend automatically send it back to the frontend ?
    or do i have to configure the middleware route.ts or somth*?
    Mina Nagy Zaki
    @mnzaki
    @agruener2000 hi! sorry for the very late reply......
    We're on rinkeby network. You can find that information in the jolocom registry code: https://github.com/jolocom/jolo-did-method/blob/master/jolo-did-registry/ts/index.ts
    Mina Nagy Zaki
    @mnzaki
    @iwTGBs it's not exactly automatic, there is some code to do that in the generic backend
    Which flow are you implementing?
    In either case there is a point at which this happens: await setStatusDone(redis, nonce)
    This is important because it triggers the code here to run: https://github.com/jolocom/generic-backend/blob/52765fdf15b8a5e9f840b269b927aa0eb477bac9/src/sockets.ts#L80
    which will send data through the socket, and I think that's what you are missing!
    This code is triggered by changes being made to redis (that's basically what watchDbForUpdate is for)
    Johannes
    @iwTGBs
    which one of the two is used if Frontend requests email on authentification , as defined in config.ts with / Credentials required during authentication /
    export const currentCredentialRequirements = ['email']. i assume thats the setting if an /authenticate/ get request comes in. wallet scans code and sends email to backend for pass to frontend . is that CredentialShare or CredentialOffer.
    Mina Nagy Zaki
    @mnzaki
    That is actually for CredentialShareflow on the wallet, which is used in the controllers/registration.ts code.
    Note that the backend code does not send any data or credentials back to the frontend after success!
    You must do that manually if you want/need to.
    The backend will only send a success message over the websocket
    Johannes
    @iwTGBs
    The backend will only send a success message over the websocket
    does it send that back to the Frontend? because in that case my Frontend doesnt even receive a success message while its listening.
    agruener2000
    @agruener2000
    @mnzaki Thanks a lot!
    Joerg
    @joerasa
    Problem: Deep link to to Jolocom Wallet app fails.
    Background: I wanted to use an service that was built a year ago and was running until x-mas without problems.
    It is based on jolocom "jolocom-lib": "^3.0.0",
    Meanwhile wallet creation fails with exeption.
    Did the interface change?
    const registry = JolocomLib.registries.jolocom.create(); const vaultedKeyProvider = JolocomLib.KeyProvider.fromSeed(didSeed, this.password); registry.authenticate( vaultedKeyProvider, {derivationPath: JolocomLib.KeyTypes.jolocomIdentityKey, encryptionPass: this.password}) .then((identityWallet) => { this.wallet = identityWallet; });
    Joerg
    @joerasa
    I tried Jolocom wallet 1.6 and 1.7. 1 and 1.8.0
    The problem is with the wallet creation of the service not with the mobile phone
    Mina Nagy Zaki
    @mnzaki
    Hello @joerasa!
    Can you share the exception/error message you are getting?
    if you haven't updated to jolocom-lib ^4.0.0 then normally nothing should have changed in a breaking way :D
    Joerg
    @joerasa
    '(node:24) UnhandledPromiseRejectionWarning: Error: Wallet undefined!
    at JolocomService.createAuthRequest (/buergeridentitaet/build/services/JolocomService.js:49:19)
    at Namespace.authRequest.on (/buergeridentitaet/build/routes/socket.js:22:18)
    at Namespace.emit (events.js:198:13)
    at Namespace.emit (/buergeridentitaet/node_modules/socket.io/lib/namespace.js:213:10)
    at /buergeridentitaet/node_modules/socket.io/lib/namespace.js:181:14
    at process._tickCallback (internal/process/next_tick.js:61:11)
    (node:24) 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: 65)
    '
    function registry.authenticate fails in line 49,
    There is no catch implemented if wallet creation fails. Therefore the exeption
    Mina Nagy Zaki
    @mnzaki
    @joerasa can you please confirm the installed/running version of jolocom-lib? NOTE: I mean the actual version, not the dependency entry. You can check with something like:
    grep version /buergeridentitaet/node_modules/jolocom-lib/package.json
    Mina Nagy Zaki
    @mnzaki
    Also, what is in JolocomService.js:49 ?
    Is that the code you shared above?? If not, then can you please share a snippet of code around that part in JolocomService.js?
    it is a little unclear where that new Error("Wallet undefined") is being thrown.....
    Chinmay Patel
    @ChinmayPatel
    I've been tasked to explore Jolocom as a Self Sovereign Identity platform. Over the next few days, I'll be setting up the environment and building a prototype from the SDK. I'll be starting from https://github.com/jolocom/jolocom-lib, https://github.com/jolocom/jolocom-sdk, https://gitlab.com/jolocom/municipal-service, https://github.com/jolocom/generic-backend, and https://gitlab.com/jolocom/municipal-service. If there are any other starting points, please let me know.
    If possible, I'll be more focused on creating a CLI tool compared to the UI parts.
    Chinmay Patel
    @ChinmayPatel

    Quick question, is there a comparison between Jolocom other SSI solutions?
    1 reply
    Mina Nagy Zaki
    @mnzaki
    Hello @ChinmayPatel !
    Currently the most up to date demo would be using https://github.com/jolocom/generic-backend/tree/interaction-demo https://github.com/jolocom/generic-frontend/tree/interaction-demo
    The demos are not integrated with the SDK yet (it's under development) Please join https://gitter.im/jolocom/jolocom-sdk for updates soon!
    Chinmay Patel
    @ChinmayPatel
    Gotcha. Thank you.
    Chinmay Patel
    @ChinmayPatel
    very handy.
    Thank you for prompt responses.
    Chinmay Patel
    @ChinmayPatel
    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?
    2 replies
    oops, I should post it to the jolocom-sdk conversation. I'll do so.
    Sean
    @blazedarwin
    Sharing some updates on a couple upcoming dev-focused events where Jolocom is involved — we hope you can join us!

    RustConf

    IIW

    • This past April we sponsored the Documentation Center at the 30th Internet Identity Workshop...and we're excited to share that the Book of Proceedings is now out!
    • Our team is proud to continue supporting the biannual community conference with Jolocom as an official sponsor behind the IIW Documentation Center once again. Registration
    IraNezhynska
    @IraNezhynska

    Hey community,
    We are giving away 4 tickets for the upcoming RustConf in return of 30min of your time.

    Jolocom design team is doing user research, and we are looking for four developers to interview tomorrow.
    If you are…

    • a fullstack / backend dev
    • interested in web 3.0 and blockchain
    • eager to support and use OSS
    • developing secure and privacy-preserving software
    • (bonus) experienced in using decentralized protocols.

    and want to attend RustConf,

    please let us know :)

    thomasmodeneis
    @thomasmodeneis
    @thomasmodeneis
    hello everyone
    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 ?
    thomasmodeneis
    @thomasmodeneis
    anyone here ?
    harshitg9715
    @harshitg9715

    Hi all,
    I am trying implement Jolocom SDK in react-native, can someone assist me with creation of self-signed credentials like email and name.
    here is what I have done so far:

    • created a 2 agents alice (jolo) and bob(jun)
    • updated alice, public profile.
    • I used bob.idw.create.credential() to create credentials, how do I this add it to the wallet ?

    Objective is to request self-signed email and name credentials from bob.

    Herman-dw
    @Herman-dw
    We are trying to create a Skills Wallet and would like to use the jolocom app for that. We would like to add Skills defined in ESCO or O*net to the jolocom wallet based on a training credential. To make a start we are trying to get the demo version working on a local docker. Can we get in touch for technical questions about this?
    2 replies
    Datafluisteraar
    @sgort
    image.png

    Hi, Steven here. I am working for the Dutch government on SSI solution (s) and I want to demonstrate the interactions demo of Jolocom for educational purposes. However, I am just not geek enough to be able to do that without help. I would like to use the HTTP (ie non SSL) version, but have no idea how to get a staging build of the SmartWallet on my Samsung. Before I get lost in endless google, here's the question: is there a staging build available with instructions for dummies on how to use it?

    I have already reached the point where the service agent runs in combination with the frontend and that I can communicate with the SmartWallet. However, that still goes wrong because I don't use SSL ...

    Mina Nagy Zaki
    @mnzaki

    @sgort hello Steven!
    I have just made a staging build for the SmartWallet v1.11.1 available for download here: https://jolocom.io/wp-content/uploads/smartwallet/smartwallet-staging-1.11.1.apk

    If you have any feedback about any other difficulties that you had to go through I'd love to hear it so we can make further updates to the README! (gonna add a link to the staging build in there right away :D)

    Mina Nagy Zaki
    @mnzaki
    As for instructions on how to install it, just follow instructions for installing an APK file, something like this: https://www.wikihow.com/Install-APK-Files-from-a-PC-on-Android
    Datafluisteraar
    @sgort
    image.png
    10 replies