Update migration mechanism
This commit is contained in:
parent
9b2ca3cdfe
commit
1f8cfd5729
1 changed files with 6 additions and 10 deletions
|
@ -21,14 +21,11 @@ to the Identity Server until the account data has been fetched from the server.
|
||||||
Once it has the account data, it SHOULD check for the presence of the
|
Once it has the account data, it SHOULD check for the presence of the
|
||||||
`m.identity_server` key. If present, the `base_url` in this key SHOULD be used
|
`m.identity_server` key. If present, the `base_url` in this key SHOULD be used
|
||||||
as the Identity Server base URL for the duration of the login session. If this
|
as the Identity Server base URL for the duration of the login session. If this
|
||||||
key is not present, the client SHOULD populate it with the ID Server URL
|
key is not present, the client SHOULD use whatever value it would have used prior
|
||||||
that was or would have been used in the login/registration process. This could
|
to this MSC. It should not update the account data in this situation.
|
||||||
be either from user input, a .well-known lookup, or a default in the client.
|
|
||||||
|
|
||||||
Client SHOULD listen for changes in the `m.identity_server` account data value
|
Client SHOULD listen for changes in the `m.identity_server` account data value
|
||||||
and update the URL that they use for ID Server requests accordingly unless
|
and update the URL that they use for ID Server requests accordingly.
|
||||||
the login session and choice of ID Server base URL predates this change, in
|
|
||||||
which case they SHOULD continue to use the value they are currently using.
|
|
||||||
|
|
||||||
Clients can offer a way for users to change the ID server being used. If they
|
Clients can offer a way for users to change the ID server being used. If they
|
||||||
do, the client MUST update the value of `m.identity_server` accordingly.
|
do, the client MUST update the value of `m.identity_server` accordingly.
|
||||||
|
@ -43,10 +40,9 @@ account data entry to `null`.
|
||||||
|
|
||||||
### Transition Period
|
### Transition Period
|
||||||
|
|
||||||
Clients currently logged in with a value configured for the ID Server base
|
Clients will continue to use whatever IS URLs they currently use until the
|
||||||
URL SHOULD use the value from `m.identity_server` if it exists or is created,
|
user sets one explicitly, at which point it will be written to account data
|
||||||
but otherwise continue to use the URL they had previously. They MUST NOT
|
and all clients will start using this value.
|
||||||
populate the `m.identity_server` with their current ID Server base URL.
|
|
||||||
|
|
||||||
## Tradeoffs
|
## Tradeoffs
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue