Converting CentralAuthUtils to use DI in T270828 was a good first step in making CA use dependency injection, but it still throws a bunch of unrelated tools into one massive service. This has the potential to cause issues similar to T273296 in the future. I would propose splitting it up to multiple smaller services each doing one thing. From a very quick look this could look something like:
- one service for database connections
- one for session handling, tokens either on this one or a separate one
- unsure about misc stuff, this includes setP3P, memcKey, getKeyValueUponExistence, and (non-forced) account autocreation