Authors: Jean-Sébastien Pédron (js.pedron@meetic-corp.com).
The module exmpp_server_sasl implements the receiving entity side of SASL authentication.
Note that it doesn't implement SASL, only feature negotiation at the XMPP level.
challenge/1 | Prepare a <challenge/> element with the given challenge. |
failure/0 | Prepare a <failure/> element. |
failure/1 | Prepare a <failure/> element. |
feature/1 | Make a feature announcement child. |
next_step/1 | Extract the response that the initiating entity sent. |
success/0 | Prepare a <success/> element. |
challenge(Challenge) -> Challenge_El
Prepare a <challenge/>
element with the given challenge.
Challenge
will be Base64-encoded by this function.
failure() -> Failure
Prepare a <failure/>
element.
failure(Condition) -> Failure
Prepare a <failure/>
element.
feature(Mechanisms) -> Feature
throws {sasl, feature_announcement, invalid_mechanisms_list, []} | {sasl, feature_announcement, invalid_mechanism, Mechanism}
Make a feature announcement child.
The result should then be passed toexmpp_stream:features/1
.
next_step(Xmlel::El) -> Type
throws {sasl, next_step, unexpected_element, El}
Extract the response that the initiating entity sent.
Any response data is Base64-decoded.success() -> Success_El
Prepare a <success/>
element.
Generated by EDoc, Jan 21 2011, 01:43:53.