Description

We need to think about how we are going to manage all these keys for all of the different wikis. @dang correctly identified that we can't check these into git. I think we have a few options and we probably want to have a separate key per site to prevent across site attacks:

• we could have the API generate and send a key to Mediawiki
  • this is probably the neatest way and we can set the whole key in $wgOAuth2PrivateKey and $wgOAuth2PublicKey as per https://www.mediawiki.org/wiki/Extension:OAuth#Configuration
  • this means we need to add these as two new settings to the API (see https://github.com/wbstack/api/blob/main/app/WikiSetting.php)
  • then generate content for them at wiki creation time (c.f. https://github.com/wbstack/api/blob/7b1f1dec2481d2503d88966cbbc25de43df2dda2/app/Http/Controllers/WikiController.php#L102)
  • to generate this content we'd need to do some research about how to create these keypairs in PHP. Shelling out and creating them using ssh-keygen/openssl see https://oauth2.thephpleague.com/installation/#generating-public-and-private-keys) is possible but would probably require extra logic to write these to some temporary place and then read them in.
• We could generate and store a key in a k8s secret; mount them all into the MW pods and then have the API pass the correct path to the right key
  • this probably will result in a crazy amount of secrets that need to be mounted into a single worker container

@dang will research how to generate a suitable public/private keypair purely in our platform api