Accept JWT tokens authorizing kick, join messages #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You can now send a JWT token with join and (brand new) kick signalling messages. The tokens currently have no effect, and the kick message does nothing yet. However, if provided, they will be validated against the signing key provided in the configuration file, and the log will show whether validation succeeded or failed. This should help us test things out before we actually start putting things behind auth barriers.
The signing key should be provided in DER format in a path given by the
auth_key
configuration key. For example, to generate a keypair (via):