joomla users with 'migrated' password

[alexalecu]

Can someone help me understand the bridge registration mechanism ? Because, this is what I see when i'm looking at the jos_user table:

I don't understand why those users have the password 'migrated' instead of the hash of the real one.
Also, I don't realize why there are entries in this table with no name, username and email values (like the ones in the screenshot), and why they have the same hash for the password ?
In the case of the 'migrated' password, is Joomla aware of the actual user password or not ? If yes, how ?
I guess these are entries that are not reported into the users list in Joomla admin interface. Because there, I see that there are 7 pages of users in list, but actualy only the first 5 are filled with users, the rest of 2 doesn't contain anything.

p.s. I've read the Orstion replies from:
- http://www.simplemachines.org/community/index.php?topic=74402.msg502455#msg502455
- http://www.simplemachines.org/community/index.php?topic=75579.msg508623#msg508623
- http://www.simplemachines.org/community/index.php?topic=63182.msg478459#msg478459
but I don't really understand it.

[Kindred]

Well, the migrated password is SOP...   when a user exists in SMF but not in Joomla, the user is created in Joomla. However, the password for SMF is *ONLY* available during the login process. So, until the user logs in using the SMF bridge login module, Joomla actually has no idea what the user's password is.

The first time they login using the bridge login module, their password will be set correctly in Joomla...
but honestly, as long as the bridge is active, the joomla password makes no difference (except for people with access to the Joomla back-end)

As for the blank use info...   I think this is a bug somewhere in your system....  it is no proper behaviour.

[alexalecu]

Thanks for your explanations, I now understand the registration process watched from the bridge perspective.
So, when an user registers itself into the system, the bridge creates an entry in the jos_user table, such as:
252 | anathema | anathema | [email protected] | migrated | the_rest_of_the_fields_follow
This entry remains like this until the user click on the link in the confirmation mail (in order to confirm the new user creation), and he enters the username and password in order to login into the system. Then, the password field from this entry in the jos_user table is changed from 'migrated' into the hash of the actual password.
Am I right ?

You suggested that I might have a bug into my system: but, if you take here:
http://www.simplemachines.org/community/index.php?topic=63182.msg478275#msg478275
you'll see that another user has posted a screenshot for the jos_user table, containing an entry with empty fields...

p.s. I'll also take a look at my testing system (containing aprox. the same data, but created under different circumstances: this one is the live system, upgraded from joomla 1.0.0 + smf 1.0.5 + bridge 3.19a_stable to joombla 1.0.7 + smf 1.1 rc2 + bridge 1.1.2, and the other system is created from scratch: joombla 1.0.7 + smf 1.1 rc2 + bridge 1.1.2)

[alexalecu]

I've just tested the registration process on my test machine, and it behaves the same way:
- users registers itself with a new account: an entry is added to the jos_users table, with name=null, username=null, email=null
- user is activating its acount: nothing happens
- user logs in using its credentials: the old entry remains, and a new one is added to the jos_users table, and its password field is 'migrated'
- user changes its password: the password field now contains the hash of the current password

My questions are:
1. how do i get rid of the auto-generation of that jos_users table entries, with no name, username and email ?
2. how can I set the password field to the hash of the password at the moment they login for the first time using the bridge, and not when they are changing their password ?

[alexalecu]

Nobody can help me ? Because this behaviour is really annoying  ...