MultiChain Developer Q&A - Recent questions tagged rpcpassword

rpc password

Thu, 14 Mar 2019 11:06:32 +0000

Team multichain,

Guys i am little wondering why every node connected in same network has their individual rpc password?
because as i am building application on multichain so i could use my own machine rpc password even though 3 node connected to my node so is there any specific reason that node connected with admin node would also neccessary rpc paassword?

I know this question is basic but still curious to understand.

Thanks.

error: incorrect rpcuser or rpcpassword (authorization failed)

Tue, 22 May 2018 09:56:51 +0000

What should i do after getting this:

MultiChain 1.0.4 Daemon (latest protocol 10010)

Starting up node...

Retrieving blockchain parameters from the seed node 10.0.2.15:7191 ...
Blockchain successfully initialized.

Please ask blockchain admin or user having activate permission to let you connect and/or transact:
multichain-cli chain1 grant 1NDYQSwedTLamNDAbj6hjY75HB5T8WLBhnsrhr connect
multichain-cli chain1 grant 1NDYQSwedTLamNDAbj6hjY75HB5T8WLBhnsrhr connect,send,receive

Specify rpc user and password at runtime

Wed, 04 Apr 2018 14:30:11 +0000

I know that the RPC username and password for the node are generated upon runtime of the blockchain in the specific node, but is it not possible to provide them as runtime parameters or something?

I haven't seen the user and password as runtime params in the official docs. I also tried specifying

-rpcuser=foo and -rpcpassword=bar but it didn't work. Still random password was generated.

My last try would be to manually replace the content of the multichain.conf file, but if I want to connect a service to the node, that means that I have to start the blockchain (in order to generate the file), then stop it, replace the content with my username and password and then start it again?

API and RPCUser/RPCPassword

Fri, 13 Oct 2017 07:54:33 +0000

Hi,

I'm building a complex system of sharing data using Multichain in Python with the Savoir Library.

Every node need to write/load/access to every data on the multichain.

I'm using the Savoir API but that require to use the RPCUser/RPCPassword of the Master Node ADMIN to connect to the other node so I have that sensible data spread everywhere and this make me nervous a little.

I know I can build a new user, give him just connect, send and receive permission, but how I can use that user with the API ?

The right way to avoid this is to build a local copy of the multichain and use local RPCUser / RPC Password ?

Thi require to download tons of data so I would prefer to let the user choice if connect to an already present node or to download all the data locally.

Thank you.

Encrypting password in multichain.conf file

Thu, 14 Sep 2017 06:02:34 +0000

Hi,

We are evaluating multichain product for a POC on blockchain and have a question. currently, i guess the rpcpassword is stored as a plain text in the multichain.conf file. This may not be secure practice as someone can read the file contents. Is there any support to use any encryption means to encrypt the password and store the encrypted password in this file? So, when making the API call the client will then have to use the same encryption key (e.g.: AES) to encrypt the plaintext password first and then post the request?

Thanks,

How can I change the standard passwork through start-up script?

Wed, 26 Jul 2017 08:46:10 +0000

Hi,

for demo purposes, I need to package a proof of concept that uses multichain. I have to use vagrant for an easy setup. if I read it correctly I can change the default network port and the default RPC port at the create stage.

The problem is that the wrapper that I use also needs the RPC user and the RPC password. The user seems to stay the same every time, but the password changes.

Is there is a way to keep configure the password just like the RPC port?

With kind regards,
Rachelle

Can we change rpcpassword?

Wed, 17 Aug 2016 09:38:02 +0000

Can we change the rpcpassword which is automatically generated on node startup? If I am doing that, I am not able to stop a node using the stop command?

Setting permissions to send and receive needs config file

Sun, 25 Oct 2015 13:56:39 +0000

Created a blockchain with default parameters. Following the tutorial, following steps were done: initializing the parent node, creating asset, and granting issue permissions to connect to a member node. However, while granting permissions to send and receive to the member node, there is an error:

"You must set rpcpassword=<rpcpassword> in the config file: ~/.multichain/grant/multichain-conf.

If the file does not exist, create it with owner-readable-only file permissions." I tried creating a blank file in a new folder created within multichain folder, but still unable to grant send and receive permissions to the member node. Could you please provide your suggestions?