Swiftdiff options
| author | Roger Planas <roger.planas@isode.com> | 2015-07-20 11:09:59 (GMT) |
|---|---|---|
| committer | Roger Planas <roger.planas@isode.com> | 2015-07-21 12:30:00 (GMT) |
| commit | 02ecf91d261276ec6f1e46b537ac0e10ebae3170 (patch) | |
| tree | ca7ac3d8c0b12870f43587f87d1bdcaf7ca0e1f5 /3rdParty/Boost/src/boost/serialization/optional.hpp | |
| parent | f10bd4cc1f570b27943d27e536d1dcfbcd55ec6a (diff) | |
| download | swift-02ecf91d261276ec6f1e46b537ac0e10ebae3170.zip swift-02ecf91d261276ec6f1e46b537ac0e10ebae3170.tar.bz2 | |
Sluift: Add set_certificate for sluift clients
This patch introduces a 'set_certificate' API for Sluift
clients, which it is just a wrapper around Swiften's
Core client setCertificate.
Test-Information:
Generated different user certificates for a user (trusted,
untrusted, invalid, expired...) and set M-Link to enable flag
'tls_require_client_cert'. Calling 'set_certificate' with these
certificates behaved as expected, either letting the Sluift
client to authenticate or not.
Also tested caling 'set_certificate' with no parameter, and the
certificate was successfully cleared (that is, client would no
longer be able to connect)
Change-Id: Ieb56d59f7f7c1c7027f0fe56905fb83ac3b25298
Diffstat (limited to '3rdParty/Boost/src/boost/serialization/optional.hpp')
0 files changed, 0 insertions, 0 deletions