Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
# Copyright 2016 OpenMarket Ltd
|
2021-10-22 04:00:52 -06:00
|
|
|
# Copyright 2021 The Matrix.org Foundation C.I.C.
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
#
|
|
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
# you may not use this file except in compliance with the License.
|
|
|
|
# You may obtain a copy of the License at
|
|
|
|
#
|
|
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
#
|
|
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
# See the License for the specific language governing permissions and
|
|
|
|
# limitations under the License.
|
|
|
|
import yaml
|
2018-07-09 00:09:20 -06:00
|
|
|
|
2021-04-06 06:48:22 -06:00
|
|
|
from synapse.config import ConfigError
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
from synapse.config.homeserver import HomeServerConfig
|
2018-07-09 00:09:20 -06:00
|
|
|
|
2021-10-22 04:00:52 -06:00
|
|
|
from tests.config.utils import ConfigFileTestCase
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
|
|
|
|
|
2021-10-22 04:00:52 -06:00
|
|
|
class ConfigLoadingFileTestCase(ConfigFileTestCase):
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
def test_load_fails_if_server_name_missing(self):
|
|
|
|
self.generate_config_and_remove_lines_containing("server_name")
|
2021-04-06 06:48:22 -06:00
|
|
|
with self.assertRaises(ConfigError):
|
2021-10-22 04:00:52 -06:00
|
|
|
HomeServerConfig.load_config("", ["-c", self.config_file])
|
2021-04-06 06:48:22 -06:00
|
|
|
with self.assertRaises(ConfigError):
|
2021-10-22 04:00:52 -06:00
|
|
|
HomeServerConfig.load_or_generate_config("", ["-c", self.config_file])
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
|
|
|
|
def test_generates_and_loads_macaroon_secret_key(self):
|
|
|
|
self.generate_config()
|
|
|
|
|
2021-10-22 04:00:52 -06:00
|
|
|
with open(self.config_file) as f:
|
2019-03-22 04:20:17 -06:00
|
|
|
raw = yaml.safe_load(f)
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
self.assertIn("macaroon_secret_key", raw)
|
|
|
|
|
2021-10-22 04:00:52 -06:00
|
|
|
config = HomeServerConfig.load_config("", ["-c", self.config_file])
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
self.assertTrue(
|
2021-10-06 08:47:41 -06:00
|
|
|
hasattr(config.key, "macaroon_secret_key"),
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
"Want config to have attr macaroon_secret_key",
|
|
|
|
)
|
2021-09-23 10:03:01 -06:00
|
|
|
if len(config.key.macaroon_secret_key) < 5:
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
self.fail(
|
|
|
|
"Want macaroon secret key to be string of at least length 5,"
|
2021-09-23 10:03:01 -06:00
|
|
|
"was: %r" % (config.key.macaroon_secret_key,)
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
)
|
|
|
|
|
2021-11-23 08:21:19 -07:00
|
|
|
config2 = HomeServerConfig.load_or_generate_config("", ["-c", self.config_file])
|
|
|
|
assert config2 is not None
|
2016-06-09 11:50:38 -06:00
|
|
|
self.assertTrue(
|
2021-11-23 08:21:19 -07:00
|
|
|
hasattr(config2.key, "macaroon_secret_key"),
|
2016-06-09 11:50:38 -06:00
|
|
|
"Want config to have attr macaroon_secret_key",
|
|
|
|
)
|
2021-11-23 08:21:19 -07:00
|
|
|
if len(config2.key.macaroon_secret_key) < 5:
|
2016-06-09 11:50:38 -06:00
|
|
|
self.fail(
|
|
|
|
"Want macaroon secret key to be string of at least length 5,"
|
2021-11-23 08:21:19 -07:00
|
|
|
"was: %r" % (config2.key.macaroon_secret_key,)
|
2016-06-09 11:50:38 -06:00
|
|
|
)
|
|
|
|
|
2016-02-09 09:23:11 -07:00
|
|
|
def test_load_succeeds_if_macaroon_secret_key_missing(self):
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
self.generate_config_and_remove_lines_containing("macaroon")
|
2021-10-22 04:00:52 -06:00
|
|
|
config1 = HomeServerConfig.load_config("", ["-c", self.config_file])
|
|
|
|
config2 = HomeServerConfig.load_config("", ["-c", self.config_file])
|
|
|
|
config3 = HomeServerConfig.load_or_generate_config("", ["-c", self.config_file])
|
2021-11-23 08:21:19 -07:00
|
|
|
assert config1 is not None
|
|
|
|
assert config2 is not None
|
|
|
|
assert config3 is not None
|
2021-10-06 08:47:41 -06:00
|
|
|
self.assertEqual(
|
|
|
|
config1.key.macaroon_secret_key, config2.key.macaroon_secret_key
|
|
|
|
)
|
|
|
|
self.assertEqual(
|
|
|
|
config1.key.macaroon_secret_key, config3.key.macaroon_secret_key
|
|
|
|
)
|
Error if macaroon key is missing from config
Currently we store all access tokens in the DB, and fall back to that
check if we can't validate the macaroon, so our fallback works here, but
for guests, their macaroons don't get persisted, so we don't get to
find them in the database. Each restart, we generate a new ephemeral
key, so guests lose access after each server restart.
I tried to fix up the config stuff to be less insane, but gave up, so
instead I bolt on yet another piece of custom one-off insanity.
Also, add some basic tests for config generation and loading.
2016-02-04 18:58:23 -07:00
|
|
|
|
2016-02-22 09:01:29 -07:00
|
|
|
def test_disable_registration(self):
|
|
|
|
self.generate_config()
|
|
|
|
self.add_lines_to_config(
|
|
|
|
["enable_registration: true", "disable_registration: true"]
|
|
|
|
)
|
|
|
|
# Check that disable_registration clobbers enable_registration.
|
2021-10-22 04:00:52 -06:00
|
|
|
config = HomeServerConfig.load_config("", ["-c", self.config_file])
|
2021-10-04 05:18:54 -06:00
|
|
|
self.assertFalse(config.registration.enable_registration)
|
2016-02-22 09:01:29 -07:00
|
|
|
|
2021-11-23 08:21:19 -07:00
|
|
|
config2 = HomeServerConfig.load_or_generate_config("", ["-c", self.config_file])
|
|
|
|
assert config2 is not None
|
|
|
|
self.assertFalse(config2.registration.enable_registration)
|
2016-06-09 11:50:38 -06:00
|
|
|
|
2016-02-22 09:01:29 -07:00
|
|
|
# Check that either config value is clobbered by the command line.
|
2021-11-23 08:21:19 -07:00
|
|
|
config3 = HomeServerConfig.load_or_generate_config(
|
2021-10-22 04:00:52 -06:00
|
|
|
"", ["-c", self.config_file, "--enable-registration"]
|
2016-02-22 09:01:29 -07:00
|
|
|
)
|
2021-11-23 08:21:19 -07:00
|
|
|
assert config3 is not None
|
|
|
|
self.assertTrue(config3.registration.enable_registration)
|
2016-02-22 09:01:29 -07:00
|
|
|
|
2019-09-06 09:45:51 -06:00
|
|
|
def test_stats_enabled(self):
|
|
|
|
self.generate_config_and_remove_lines_containing("enable_metrics")
|
|
|
|
self.add_lines_to_config(["enable_metrics: true"])
|
|
|
|
|
|
|
|
# The default Metrics Flags are off by default.
|
2021-10-22 04:00:52 -06:00
|
|
|
config = HomeServerConfig.load_config("", ["-c", self.config_file])
|
2021-09-23 10:03:01 -06:00
|
|
|
self.assertFalse(config.metrics.metrics_flags.known_servers)
|
2021-11-18 11:56:32 -07:00
|
|
|
|
|
|
|
def test_depreciated_identity_server_flag_throws_error(self):
|
|
|
|
self.generate_config()
|
|
|
|
# Needed to ensure that actual key/value pair added below don't end up on a line with a comment
|
|
|
|
self.add_lines_to_config([" "])
|
|
|
|
# Check that presence of "trust_identity_server_for_password" throws config error
|
|
|
|
self.add_lines_to_config(["trust_identity_server_for_password_resets: true"])
|
|
|
|
with self.assertRaises(ConfigError):
|
|
|
|
HomeServerConfig.load_config("", ["-c", self.config_file])
|