There is also a new auth type jatNoAuth which will establish a connection to the server, but will not register the new user, OR send any authentication tokens. Use this auth-type in conjunction with the SendRegister and new OnRegFields event to handle "dynamic user registration". (see SendRegister for more info).
NOTE: NEW AUTH functionality as of Feb 28, 2002
IJabberSession now has a new property called CustomAuth. By setting this property, JabberCOM will not send out the iq-set which actually authenticates the user. Instead, it will fire the OnConnected event when this tag would normally be sent out.
At this point in the authentication procedure, the client application can use GetAuthTag to obtain a pre-populated version of the iq-set which would normally be sent to the server. Using this tag, the client application can add elements, or modify the tag in any way before using SendAuthTag to actually send to the jabber server which would then authenticate the user.
NOTE: Browsing will eventually replace the entire Agents interface. When working with 1.4 servers, you should be able to Browse the server JID (jabber.org) and receive all of the available services. 1.4 Servers still support the old agents list but this list is begin generated (built) based on the browse objects the server knows about.