5-2. Auth Component
Last updated
Last updated
src/components/Auth.js
:
Auth
component1) Background
2) Auth
component overview
3) Auth
component feature: User can input private key to login.
4) Auth
component feature: User can import a keystore file and input password to log in.
5) Auth
component feature: User can logout and clear the wallet instance information from the browser.
In a blockchain-based app, we usually interact with smart contracts.
There are 2 types of interactions with a contract.
1) Read data from a contract.
2) Write data to a contract.
It is cost-free to read data from contracts. On the other hand, there is a cost for writing data to contract.
cf) Sending a transaction
Writing data to contracts or blockchain is called 'sending a transaction'.
For example, if you send 5 KLAY to your friend, you could think of it as writing data to the blockchain that I sent 5 KLAY to my friend
.
Calling a contract method is the same. You could think of it as writing data onto the contract that I set variable X to 100
. All actions related to writing data to blockchain or contract is called sending a transaction
.
To write data to contract, you should have a Klaytn account which has KLAY to pay for the transaction fee.
Auth
component helps you log in to your app.
Auth
component overview'Auth.js'
component is the longest code in our tutorial app, so we will break down the code and go over one by one.
This component provides the following user interface.
Main features are: 1) User can input private key to login. 2) User can import a keystore file and input password to login. 3) User can logout and clear the wallet instance information from the browser.
Auth
component feature: User can input private key to login.integrateWallet
method is needed to login with private key.
integateWallet
function takes privateKey
as an argument, use it to generate a wallet instance.
Line 1: const walletInstance = cav.klay.accounts.privateKeyToAccount(privateKey)
It stores the wallet instance made by privateKeyToAccount
API to the walletInstance
variable.
Line 2: cav.klay.accounts.wallet.add(walletInstance)
To send a transaction, you should add a wallet instance to caver through cav.klay.accounts.wallet.add(walletInstance)
.
Line 3: sessionStorage.setItem('walletInstance', JSON.stringify(walletInstance))
sessionStorage.setItem
is a browser API used for storing a value to the browser's session storage.
Since we want not to lose our logged-in status even we refresh our tutorial app page, we stored our wallet instance to the session storage as a JSON string.
cf) Items in the session storage disappears when the user closes the browser tab.
Line 4: this.reset()
It resets the current component's state to the initial state to clear your input.
For further information about privateKeyToAccount
API of caver-js, see caver.klay.accounts.privateKeyToAccount
Auth
component feature: User can import keystore file and input password to login.handleImport
and handleLogin
methods are needed to login with a keystore and password.
To import a file from user, we use FileReader
browser API.
e.target.files[0]
contains meta information for the file. To read the content of the file, we call fileReader.readAsText(keystore)
API.
After calling fileReader.readAsText(keystore)
, fileReader.onload
function fires to take the content of the file as e.target.result
.
After importing the keystore file, we get password input.
cf) Keystore contains an encrypted private key. We need the matching password to decrypt the keystore to get the actual private key. WARNING Don't expose your keystore file to another person!
Fill password into <input>
element. Entered value will be stored as password
state through handleChange
method.
Both the keystore file and its password are ready. We can now decrypt the keystore file to extract the private key through cav.klay.accounts.decrypt(keystore, password)
API.
This API returns a wallet instance containing the private key. After importing the private key, we can use integrateWallet
method we've visited earlier.
For further information about decrypting keystore file with password, see caver.klay.accounts.decrypt
Auth
component feature: User can logout, remove wallet instance information from browser.'logout' means removing the wallet instance from the browser and caver.
cav.klay.accounts.wallet.clear()
removes all wallet instances from caver.
sessionStorage.removeItem('walletInstance')
removes the wallet instance from the browser's session storage.
For further information about clearing a wallet instance from caver-js, see caver.klay.accounts.wallet.clear