Can't change "identity-url" after bootstrap
Bug #1788853 reported by
Tytus Kurek
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It looks like it is impossible to change "identity-url" after bootstrap:
$ juju controller-config identity-url="http://
ERROR can't change "identity-url" after bootstrap
This is blocking an introduction of the identity manager for all existing deployments - they would need to be re-deployed.
Moreover, changing the URL of the identity manager or switching from http to https is also not possible.
There must be a way to change "identity-url" after bootstrap. At this point even hacking Juju database doesn't work.
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
| Changed in juju: | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in juju: | |
| status: | Incomplete → Expired |
| Changed in juju: | |
| status: | Expired → New |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| importance: | Medium → Wishlist |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| importance: | Wishlist → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This goes into a deeper nest as any existing entities (models, etc) and who owns then turns into different user accounts. There's no mechanism to tie existing Juju users in the DB to matching ones from the external identify service and so this is much deeper than changing the url which is locked for this very reason.