0

I have locally created a DApp in Solidity for Ethereum framework. I have a smart contract, a js file (using web3 API) and html file. What I want to achieve is the login feature since the smart contract will return different results depending from the caller. I know I can access the functions using the Mist Browser, but I want a complete custom 'user interface'. Currently, I am simulating the login by manually specifying the 'logged in' user using web3.eth.accounts[0] in the javascript file where the contract functions are called.

I have seen this answer: Handling user profiles in Ethereum DApps but it mentions IPFS and Json file and does not seem the solution for me.
My questions are:

  • Should I handle the login (registration, create of Ethereum account) myself like a custom wallet generating the private, public keys and signing of the transactions?

    Or

  • Is there a feature in MetaMask or Mist Browser that offers also the deploying of html and js?

  • This is an article for SWARM as a distributed storage for html, js etc https://blog.ethereum.org/2016/12/15/swarm-alpha-public-pilot-basics-swarm/ but I cannot figure out if it the case for my problem.

Which of my points can be a solution for login in DApps?

Community
  • 1
  • 1
Angie
  • 21
  • 6

1 Answers1

1

This largely depends on a number of factors including what your definition of login or authentication means. If you're truly talking just about registration or creation of an Ethereum account (public/private key pairing), I would suggest using an external wallet such as MetaMask and not storing the private keys on the nodes as the simplest route.

MetaMask will inject an instance of web3 into the browser where the user can connect to the appropriate Ethereum network and interact with your DApp via their own self-managed account(s).

You could also handle this scenario utilizing a library such as ethereumjs-wallet. However, in doing so you will then have to securely manage the private keys off-chain on the behalf of the user. A benefit of this method would allow the end-user to be able to authenticate via any IDP and have their public address tied to that identity off-chain.

Ben
  • 2,441
  • 1
  • 12
  • 16
  • From your first suggestion I finally understood that I was missinformed about the web.eth.accounts[0] thinking it was only for development purposes. Actually from this link: [link] (https://github.com/MetaMask/faq/blob/master/DEVELOPERS.md#partly_sunny-web3---ethereum-browser-environment-check) the phrase sums everything up: _When a user selects an account in MetaMask, that account silently becomes the web3.eth.accounts[0] in your JS context, the only member of the web3.eth.accounts array._ – Angie Dec 26 '18 at 23:07
  • 1
    @Angie, correct. In this case you could have your DApp handle the authentication actions based upon the existence or lack thereof `web3.eth.accounts[0]`. – Ben Dec 26 '18 at 23:24