Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Overhaul tracker keys: option to disable auth key expiration #988

Merged
merged 2 commits into from
Aug 1, 2024
Merged

Overhaul tracker keys: option to disable auth key expiration #988

merged 2 commits into from
Aug 1, 2024

Commits on Aug 1, 2024

  1. feat: [torrust#978] add a config option to disable cheking keys' expi… 

    …ration

When the tracker is running in private mode you can disable checking
keys' expiration in the configuration with:

```toml
[core]
private = false

[core.private_mode]
check_keys_expiration = true
```

All keys will be valid as long as they exist in the database.
    @josecelano
    josecelano committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    e8e935c View commit details
    Browse the repository at this point in the history

  2. feat: [torrust#978] add semantic validation for configuration 

    The section [core.provate_mode] can be inlcuded in the configration TOML
file only if the tracker is running in private mode (`private = true`).

This commits adds that validation and makes it possible to add more
semantic validations in the future.

Semantic validations are validations that depend on more than one value.
Like the one added, it could be any other incompatible combination.
    @josecelano
    josecelano committed Aug 1, 2024
    Configuration menu
    Copy the full SHA
    d7dfc3b View commit details
    Browse the repository at this point in the history