when using only rpcauth it's still checking for rpcpassword.
my bitcoin.conf looks something like this
listen=0
server=1
txindex=1
rpcallowip=10.1.1.3/32
rpcbind=10.1.1.2
rpcauth=user:pass
I used share/rpcauth/rpcauth.py to generate rpcauth
2020-05-17T01:33:04Z No rpcpassword set - using random cookie authentication.
2020-05-17T01:33:04Z Generated RPC authentication cookie /mnt/media/files/bitcoin/.cookie
2020-05-17T01:33:04Z Using rpcauth authentication.
I see this in log. is this expected behavior? I'd expect the cookie to not get generated when using rpcauth.
Also, if rpcbind is above rpcallowip in the config, rpc breaks:
2020-05-14T02:54:10Z WARNING: option -rpcallowip was specified without -rpcbind; this doesn't usually make sense
