[Psi-devel] Are there any clients supporting SASL authorization identities?

[textshell-I1QKlO@neutronstar.dyndns.org]

On Wed, Jul 26, 2006 at 04:56:54PM +0200, Remko Troncon wrote:
> 
> On 26 Jul 2006, at 16:51, textshell-I1QKlO at neutronstar.dyndns.org wrote:
> 
> > I wonder what's the primary use case of this...
> 
> Another use case for this (from the jdev list) is several people  
> being authorized to log in to the sales at domain.com or  
> helpdesk at domain.com account, without needing a shared password.
> 

ok, for that use case it needs to be in the account settings. 

i'm not sure what from the usebility point of view would be more logical if
it's in the account properties.
a) have Account/Jabber ID be the JID the user is loged in as. and have a
use alternete JID to authorize put somewhere else out of sight. (the
password field be at an inconsistent position, but the JID that the user
will most likely associate with the account is on the first tab)

b) do it like the protocol internaly does and have a authzid field
somewhere in the dialog. I think in that case psi would have to be changed
to use the jid from that alternate field in a lot of places. (or the
account class would at least need to swap JIDs around).


the more i think about it, a) seems to be more natural to me. But i don't
know if that's doable and if a native speaker can come up with nice labels
for the controls.

 - Martin H.