This repository was archived by the owner on Nov 4, 2024. It is now read-only.
Client certificates (with password authentication) #1488
Merged
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
# Conflicts: # rainloop/v/0.0.0/app/libraries/RainLoop/Model/Account.php
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
These changes allow RainLoop to use SSL/TLS client certificates to authenticate as well as a password. The certificate can be specified with a new "client_cert" parameter in the SSL section, which takes a pem-format file containing the certificate followed by the certificate's private key (presumably also permitting intermediate certificates to be sent, though I haven't tested that).
It's still a bit rough around the edges, but may save some time if this feature ends up in the roadmap at some point.