by

Where communities thrive


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

    @iwTGBs: that i firstly get back an QR Code from the backend and eventually but not necessarily, [...], authenticate via the QR Code in the confined spaces of my local development network?

    Not sure if this is clear but:
    To "authenticate via the QR code" the wallet will actually send HTTP requests to the backend that issued the interaction token that is encoded in this QR code, so you absolutely need the wallet to have access to the backend

    Johannes
    @iwTGBs
    @mnzaki Our service is not a server side frontend its running locally in an electron app / browser and its not accessible on the internet. therefore we need to have some server side component and we thought the backend could be that, meaning the backend keeps websockets open to both the wallet and the frontend client. Thus enabling the communication between both (Wallet and Frontend Service).
    Mina Nagy Zaki
    @mnzaki
    @iwTGBs but is your app entirely local-first? I mean you don't have any global services/backends/servers etc?
    also if your project is open source I would really appreciate taking a look :D
    Johannes
    @iwTGBs
    @mnzaki The application is "entirely and mostly" local first. At least for the purpose of authentication between wallet and frontend. Once the identity is logged-on to the frontend (which basically means that the user has demonstrated that he is in posession of the private key of the identity via the wallet and not some identity-impersonator), the frontend (which is the client UI and business logic) then is capable to log-on to a cloud service which provides the transactional data to be run/processed in the frontend client. Note : The identity (DID) needs to be pre-approved in the cloud-service by a separate permissioned process. Concerning taking a look at the source code: Yes, we will open-source the frontend in the future but its not yet done. Nevertheless we really would like to have a chat with you if it´s possible (Skype / Zoom or other means). For better mutual understanding of what we are doing ( Integration of your wallet) and regarding our requirements for your wallet for our next steps with our frontend / cloud-service.
    Johannes
    @iwTGBs
    @mnzaki You might want to know who you are talking with. For that purpose I´m giving you the link to the company´s web/online representation. So you can get sort of an insight /impression. https://difacturo.com/
    Mina Nagy Zaki
    @mnzaki
    @iwTGBs hey! I will try to arrange for a call soon, but apologies we are kind of busy with various things right now
    Johannes
    @iwTGBs
    @mnzaki👍
    Johannes
    @iwTGBs
    @mnzaki Hey. Following Problem: with the Swimming Pool example. Redis server is running properly. BUT: Backend Server doesn´t start. Im checked out with "git checkout feature/aKaartIntegration" as described in the Documentation and am using that standard configuraiton without change. On console logging in "server.ts" it gives me the following error when i start the backend server manually(manually, because it doesn´t start it with yarn start). Hallo
    SoftwareKeyProvider {
    encryptedSeed:
    <Buffer 78 9e 02 4e 4a 3f d4 44 f4 50 a1 1c 97 9d 3a 86 c1 8c c7 d4 62 a0 3e 58 11 f7 8e fe 10 c3 20 c4 ee 04 71 61 a6 e2 08 1b 1c 0f 1c 00 70 3c 42 54> }
    (node:17865) UnhandledPromiseRejectionWarning: Error: Could not retrieve DID Document. Returned error: project ID is required
    at JolocomRegistry.<anonymous> (/home/johannes/Desktop/generic-backend/node_modules/jolocom-lib/js/registries/jolocomRegistry.js:172:31)
    at step (/home/johannes/Desktop/generic-backend/node_modules/jolocom-lib/js/registries/jolocomRegistry.js:32:23)
    at Object.throw (/home/johannes/Desktop/generic-backend/node_modules/jolocom-lib/js/registries/jolocomRegistry.js:13:53)
    at rejected (/home/johannes/Desktop/generic-backend/node_modules/jolocom-lib/js/registries/jolocomRegistry.js:5:65)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    (node:17865) 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:17865) [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. What can i do about that?
    Using standard Login aaaaaa * 64 and battery horse staple that was provided
    in config.ts
    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.