Can't change "identity-url" after bootstrap

[Tytus Kurek]

It looks like it is impossible to change "identity-url" after bootstrap:

$ juju controller-config identity-url="http://candid.example.com:8081/"
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.

[Richard Harding (rharding)]

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.

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

[Benjamin Allot (ballot)]

Reopening this bug, as this is really important if we are to use JAAS to control our multiple juju deployments (several thousand of models).

Changing this url might be key as if any change is required on the JAAS (candid/jimm) aspect, migrating the models is out of the picture as a workaround solution.