[jdev] Custom authentication errors

Peter Saint-Andre stpeter at jabber.org
Wed May 31 10:15:56 CDT 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vinod Panicker wrote:
> On 5/30/06, Peter Saint-Andre <stpeter at jabber.org> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Vinod Panicker wrote:
>> > Hi,
>> >
>> > I have a use case where the server needs to return specific messages
>> > to the client in case of authentication failures.  I looked at the
>> > schema and it's pretty restrictive in what is being allowed during the
>> > sasl handshake.
>> >
>> > Would it make sense to relax the schema to allow text between the
>> > error conditions, say like this -
>> >
>> > <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
>> >  <temporary-auth-failure>Server under maintenance, please try after
>> > some time.</temporary-auth-failure>
>> > </failure>
>> > </stream:stream>
>>
>> I think is would be better to emulate the structure of stanza errors:
>>
>> <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
>>  <temporary-auth-failure/>
>>  <text>Server under maintenance, please try after
>> some time.</text>
>> </failure>
>> </stream:stream>
> 
> Sounds good to me.  Could we also have the <text/> element within a
> <success/> element too?  Thats another use case that I have.  

Yes, I think we would add an OPTIONAL <text/> element in both.

> Would
> you be pushing these changes in 3920bis?

That's where they will go, yes.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEfbMsNF1RSzyt3NURAvM4AJ9O+ZXIOzaMcHrmbIB6YME3gioNMwCeNBHg
O0zpHZp6hDQYfS7URcr8B0k=
=C7xH
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20060531/8dd8902a/attachment-0002.bin>


More information about the JDev mailing list