Enable user/password login

Bug #1074423 reported by Gary Poster on 2012-11-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Benji York

Bug Description

See bug 1074419

It should be possible for the GUI to accept authentication requests from the websocket via some mechanism; display the authentication challenge; and log in.

Kapil has encouraged us to start this before bug 1074419 is completed, because he has given us the wire protocol for the authentication challenge:


Note that we also want to support a non-authenticated approach, which will behave as it does now (passing provider_type and default_series immediately on connection).

When we get the login-required state, we can require a login with an interceptor in the dispatch rules. From Kapil: """a route match to "*" that doesn't let the next rule match proceed if login isn't there.. it will just do the login dialog display."""

We should get a UI design for this, but it is simple enough in functionality that we can get something working before then, and add a separate card for matching it to the desired design later.

Related branches

Gary Poster (gary) on 2012-11-30
description: updated
Gary Poster (gary) wrote :

Use lp:~hazmat/juju/rapi-login for a branch of Juju that supports the expected behavior.

Benji York (benji) on 2012-12-21
Changed in juju-gui:
assignee: nobody → Benji York (benji)
milestone: none → 0.1.1
status: Triaged → In Progress
Benji York (benji) on 2013-01-07
Changed in juju-gui:
milestone: 0.1.1 → 0.1.3+build.302
Gary Poster (gary) on 2013-01-15
Changed in juju-gui:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers