pep/xmpp-rs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
xmpp-rs/sasl
History
Lucas Kent 8bdd19b0ff Add SCRAM client extensions support 
The SCRAM RFC describes extensions that can be used to add extra
data into the protocol.

This commit adds support for the client scram mechanism to insert extension
data into the client messages at the locations specified by the SCRAM RFC.

Kafka utilizes these extensions when authenticating delegation tokens
over scram. Since I am writing a kafka client I would like access to
these extensions so I can support delegation tokens.

I've only added them to Scram::new not Mechanism::from_credentials
since they do not apply to other mechanisms. For my purposes this is
fine since I only need to work with scram. However it would be
limiting for other use cases, so I'm quite happy to add the extension
fields into Credentials if that was desired. For now I've left it out
since the fields would be scram exclusive and everything else in
Credentials is currently generic.
2024-05-13 23:42:22 +00:00
..
src Add SCRAM client extensions support 2024-05-13 23:42:22 +00:00
.gitignore initial commit 2017-02-27 16:08:09 +01:00
Cargo.toml Swap sasl crate from sha-1 crate -> sha1 crate 2024-05-13 13:03:33 +10:00
CHANGELOG.md sasl: 0.5.1 release 2023-08-20 21:29:51 +02:00
LICENSE sasl: Update LICENSE file to reflect changes for 0.5.0 2023-08-20 21:28:59 +02:00
README.md Update crate information 2022-12-21 09:34:04 +00:00

README.md

sasl-rs

What's this?

A crate which handles SASL authentication. Still unstable until 1.0.0.

Can I see an example?

Look at the documentation here.

What license is it under?

MPL-2.0. See LICENSE.

License yadda yadda.

Copyright 2017, sasl-rs contributors.

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/.