[2.5, RBAC] No explaination why authentication is needed when configuring RBAC
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Alberto Donato | ||
Bug Description
If you initialize MAAS with RBAC as the authentication source, you'll see this:
maas-devel:~/> sudo maas init --enable-candid --rbac-url http://
Configuring authentication
Opening an authorization web page in your browser.
If it does not open, please open this URL:
http://
Service "maas1" registered
Opening an authorization web page in your browser.
If it does not open, please open this URL:
http://
Administrator user 'user1' created
You're asked to authenticate twice, but in neither case it says why you have to authenticate. For example, for the first time, it's so that the MAAS service can be registered in RBAC. What the second authentication is for is even harder to understand.
Related branches
- Blake Rouse (community): Approve
- MAAS Lander: Approve
-
Diff: 142 lines (+48/-23)3 files modifiedsrc/maascli/init.py (+17/-11)
src/maascli/tests/test_init.py (+30/-12)
src/maasserver/management/commands/configauth.py (+1/-0)
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.5.1 |
| Changed in maas: | |
| assignee: | nobody → Alberto Donato (ack) |
| status: | Triaged → In Progress |
| summary: |
- No explaination why authentiction is needed when configuring RBAC + No explaination why authentication is needed when configuring RBAC |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| summary: |
- No explaination why authentication is needed when configuring RBAC + [2.5] No explaination why authentication is needed when configuring RBAC |
| summary: |
- [2.5] No explaination why authentication is needed when configuring RBAC + [2.5, RBAC] No explaination why authentication is needed when + configuring RBAC |
| tags: | added: rbac |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
