Enable user/password login
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-gui |
Fix Released
|
High
|
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:
http://
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
- Juju GUI Hackers: Pending requested
-
Diff: 536 lines (+286/-32)10 files modifiedapp/app.js (+49/-0)
app/modules-debug.js (+5/-0)
app/modules-prod.js (+1/-0)
app/store/env.js (+49/-7)
app/views/login.js (+59/-0)
test/index.html (+26/-22)
test/test_app.js (+7/-1)
test/test_app_hotkeys.js (+2/-1)
test/test_login.js (+86/-0)
test/test_service_view.js (+2/-1)
| description: | updated |
| Gary Poster (gary) wrote | #1 |
| Gary Poster (gary) wrote | #2 |
| Changed in juju-gui: | |
| assignee: | nobody → Benji York (benji) |
| milestone: | none → 0.1.1 |
| status: | Triaged → In Progress |
| Changed in juju-gui: | |
| milestone: | 0.1.1 → 0.1.3+build.302 |
| Changed in juju-gui: | |
| status: | In Progress → Fix Released |
Use lp:~hazmat/juju/rapi-login for a branch of Juju that supports the expected behavior.