tomusdrw
commented
6 years ago --ui-no-validation is development option and should never be used. That's also the reason why it's not present in a config file.
You're config file states:
[websockets]
...
origins = ["none"]You should leave it default or allow connections from 127.0.0.1:8180:
[websockets]
origins = ["http://127.0.0.1:8180"]
INFO
Which Parity version?: 1.8.4-beta Which operating system?: MacOS How installed?: homebrew Are you fully synchronized?: no, N/A Did you try to restart the node?: yes
actual behaviour
I am using a custom Parity Configuration file (i.e. kovan-config.toml) to run the Parity UI connected to the Kovan Test Network.
When I run
parity ui --config ./kovan-config.tomlit opens the Google Chrome browser, shows some warnings saying that it blocked connection to WebSockets from an untrusted origin, and that I was using an invalid token. But it's helpful and tells me to generate a Secure Token via the command line withparity signer new-token, and to then paste the output as the value of the "secure token" input field in the UI. But when I do that it just shows the same errors again the in terminal Parity logs. I thought that providing the following in my kovan-config.toml file would help bypass the requirement for the secure token:But the only way I can actually bypass the security window (i.e. connect to the Parity Secure API) and the warnings and get it to load Parity is to provide the flag
--ui-no-validationBut I want know what configuration option I need to add to kovan-config.toml that will achieve the same outcome, but without using the flag
--ui-no-validation. Note hat I have tried changing it toui_no_validation = truebut it still doesn't workexpected behavior
We should be able to run the Parity UI using the Kovan Network by adding a appropriate configuration options to kovan-config.toml file that would help bypass the requirement for the secure token, such as with the following options, without the need for providing any additional flags such as
--ui-no-validation:steps to reproduce
I configure Parity to use a Kovan network Node. I created a custom kovan-config.toml file by following the Parity Configuration Guide.
I create a signer account for this Kovan network to satisfy the Mining Options with the following command and provided a password for it.
This returned a random address: i.e. 0xrandom0000000000000000000000000000000000, and it created a key in my folder Users/Me/Library/Application Support/io.parity.ethereum/testnet/keys/kovan/UTC--2017-12-28T00-09-16Z--000-000
I then edited my Parity Configuration file for the Kovan Node kovan-config.toml, and changed the address I had used in the Account Options and Mining Options. i.e.
So the file became:
Then I ran the Kovan Node using my custom config
This works successfully without any UI.
But if I want to run it in the UI at http://127.0.0.1:8180/#/home, I first have to change the UI Options in my configuration file to
force = true, i.e. :I then run the Parity Node with Kovan Network with:
This opens Google Chrome browser and displays the following:
In the Bash Terminal it displays:
If I copy and paste the generated token PLmx-T4pw-KZE8-KXcO into the input field where it asks for the "secure token" in the UI, or if I go to http://127.0.0.1:8180/#/auth?token=PLmx-T4pw-KZE8-KXcO, it just shows those warnings again.
So I try and just do what it says and I run the following to generate a token from my computer and paste the output into the browser, but doing that also just shows those warnings again.
I can only get it to work when I provide the CLI flag
--ui-no-validation, but I want to avoid having to pass these flags. Instead I want to know how I can achieve the same thing and get it to work without those warnings by just providing the configuring the TOML configuration file.