No, that's not what I am looking for. I know enough clients, that have
support to authenticate using SASL. But they all transmit no
authorization id, and therefore they authorize as the same identity as
they authenticate.
SASL has the concept of authorizing as someone else as you
authenticated. But this does not seem to be supported by any Jabber
client yet. E.g. the user [EMAIL PROTECTED] could have the right to
authorize as [EMAIL PROTECTED] In that case the user [EMAIL PROTECTED]
would have to provide "[EMAIL PROTECTED]" as the authentication id, the
password for the user [EMAIL PROTECTED], and "[EMAIL PROTECTED]" as the
authentication id. But it would NOT have to know or to provide the
password for [EMAIL PROTECTED]
this is a nice feature. I would be interested to add support for that in
agsXMPP, and also add it to my test.
Alex
