Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

parity signer new-token displays old information #9073

Closed
stone212 opened this issue Jul 9, 2018 · 1 comment
Closed

parity signer new-token displays old information #9073

stone212 opened this issue Jul 9, 2018 · 1 comment
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P5-sometimesoon 🌲 Issue is worth doing soon. Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow.
Milestone

Comments

@stone212
Copy link

stone212 commented Jul 9, 2018

Before filing a new issue, please provide the following information.

I'm running:

  • Which Parity version?: 1.10.7
  • Which operating system?: Ubuntu
  • How installed?: binary (deb)
  • Are you fully synchronized?: yes
  • Which network are you connected to?: eth
  • Did you try to restart the node?: yes

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

Using the new ParityUI I am directed to create a new token. I do:

$ parity signer new-token

The new token appears and I can use it in the Parity UI. But there is also this message:

Open: http://127.0.0.1:8180/#/auth?token=FU9b-YqaT-FdRN-1dOw
to authorize your browser.

Because the browser UI does not work any more I think this message should be deleted?

@Tbaut Tbaut added the F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. label Jul 9, 2018
@Tbaut Tbaut added this to the 2.0 milestone Jul 9, 2018
@Tbaut Tbaut added the P5-sometimesoon 🌲 Issue is worth doing soon. label Jul 9, 2018
@Tbaut Tbaut added the Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow. label Jul 9, 2018
@sorpaas
Copy link
Collaborator

sorpaas commented Jul 12, 2018

This should be fixed in #8783. I don't remember we backported it to current beta or stable yet, but this will land on next beta, at least. :)

@sorpaas sorpaas closed this as completed Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. P5-sometimesoon 🌲 Issue is worth doing soon. Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow.
Projects
None yet
Development

No branches or pull requests

3 participants