Documentation for DA should say 'admin approval is incompatible'

today's patch for user.module in ldap_integration directory makes explicit this requirement as well as implementing Mark's suggestion of 'exclusive external authentication'

assigning this to myself as i am awaiting some feedback before submitting the patch for CVS review

There's no reason that this couldn't work with admin approval on.

Admin approval on would support this process:
- users can create own local system accounts, but must be approved by admin
- users using a Drupal ID skip the approval process: account is still active on RPC'd server so it is considered acceptable

Drupal.module controls the user's choice of accepting Drupal IDs or not, so even if admin approval is on, and the above process isn't implemented, a user trying to login with one shouldn't be blocked, they should be dropped into the approval process with everyone else -- at the least.

Are either of these the process in the CVS version of Drupal?

>> To qualify this outside of the bug system. Personally I'd like to have
>> the option of account creation off and external auth on, eg I want my

Drupal site to run exclusively against a jabber server. Is anybody working on the jabber.module or does anyone know why it is not in 4.4 any more?

I managed to get the 4.3 Version running. The was an issue with a foreach warning using this module. I fixed it (File attached).

I'd like to enhance the module by adding "change password" and "registration" against a jabber server. Specifying a default jabber server and using this one for authentication if no @server is given as a user name would be nice.
Currently I am a bit unsure on how the modules' functions are called. Specially in which order an with which precedence when two modules implement the same function. Can someone enlighten me?

-silence

The jabber module has been discontinued for lack of a maintainer. If you want to be the new maintainer, please apply by sending mail to drupal-devel.