Deploying with faulty PORTAL_CONFIG_KEY renders strange results

[DonMartin76]

If you deploy wicked with a different PORTAL_CONFIG_KEY (the key from deploy.envkey) than the one you used when creating the static configuration, things can start behaving really strangely; most prominent will be the following:

• reCaptcha is not validated correctly
• Google/Github login does not work ("Unauthorized"), as the client secret is not decoded correctly
• User creation does not work correctly

It would be good if the portal API could check whether the PORTAL_CONFIG_KEY is correct, e.g. by creating an encrypted field containing a static text, like "wicked.haufe.io" which always has to be present.

[DonMartin76]

Both the kickstarter and the portal-api will not verify that they have a valid config key when starting up. This will only apply after you have run and updated the static configuration once using the kickstarter 0.11.4 or later.

This will update the configuration to revision 4 and add a configKeyCheck property to the globals.json file.