Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Store identity server in Account Data and support choosing identity server integration in User Settings #10094
One thing that's not clear on this is how this should work with all the other places that specify ISes, ie. if the one you had at login time (be that from your client's default, .well-known or entered), is that then discarded in favour of using the one in your account settings? I'm going to assume so for now.
We should no longer have an IS 'supplied at login time' - rather there is a 'default' that is 'the Identity Server the client would prompt to use if asked to do something identity servery and the user has not made an active choice to use either a different identity server or no identity servrer at all'.
This 'default' could be specified in the config.json or in .well-known (I can't think of anywhere else sensible to provide this at the moment), or it could not be specified at all.
There is an unanswered question about what we do if an admin wants to provide a matrix stack with a locked-down IS choice. I think answering this question is hard, so despite the risk of our painting ourselves into a corner with the proposed, I'd like to keep a lid on this for now and tackle it if/when we have a concrete usecase to consider.