Per-client SASL certificates #1463
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3nprob
force-pushed
the
sasl-certfp
branch
2 times, most recently
from
229ba50 to
eac39bf
Compare
3nprob
force-pushed
the
sasl-certfp
branch
2 times, most recently
from
11d54b6 to
f5062c5
Compare
0.33.0
* Users can manage key and cert via ![store,remove][cert,key]` commands * Bot configured under botConfig
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This enables CertFP authentication for both users and bots. #1062 reuses the same certificate across all users. In order to make the isolation here clear, bot certificates are read from
botConfig. Users can manage their own certs and keys in a similar fashion to passwords.Adds bot commands:
storekey,removekey,storecert,removecert.