[cheesegrits]

You'll have to do this:

PHP Code:

define('DISABLE_PASSWORD_CLEARING',1); 


... in your config.php. This is not set by default, which means the md5hash() javascript routine clears the clear text password form data so only the md5 version is sent over the wire. But you may define it yourself, as per this comment in global.php:

PHP Code:

// you may define this if you don't want the password in the login box to be zapped onsubmit; good for integration
$show['nopasswordempty'] = defined('DISABLE_PASSWORD_CLEARING') ? 1 : 0; // this nees to be an int for the templates 


Although the comment is a little misleading, as it really applies to anywhere a password is submitted from the browser, like during registration or when changing passwords, not just on login.

Will you have to worry about syncronizing passwords between the corporate db and vB? i.e. if they change their vB password, will you need to update the corporate db, and vice versa? Or is it just a one off thing during registration?

-- hugh