Looks like I have to eat my words. At one point it was filling the profiles with information but I went and checked a couple of my production installs and found that it wasn't working any longer. I'm not sure when this broke as it hasn't been reported until now and the process for updating the user in the provider's code is essentially the same as it was in the 05.00.02 version.

I debugged the code and the user object I'm sending to the DotNetNuke procedure for updating the user information does contain all of missing information (address/phone/email/etc) so I'm going to have to dig into the DNN source code to try to figure out where it's going sideways and then adjust for that.

As for custom fields that are getting wiped out... I'm not sure at this point how I'm going to fix that but I have a few ideas. I need to do fix the initial problem first before I tackle that one. It may be that fixing the first problem will fix the second problem as well.

Wow... this is looking like it's going to be more fun to fix/debug than I thought. I had some time tonight and figured I'd do some testing here @ home where I have full control over the AD.

On my home domain my user objects have no information so, correctly, the profiles were populated with absolutely nothing on my development system. So I quickly filled my user's object with data and then went to test against on my dev system. Here at home it only pulls back the information from the General tab of the user object (FirstName, LastName, Display Name, Telephone Number, Email) and it also pulled the City and Province from the Address tab but nothing else. And any changes I make to those items gets updated on login.

Conversely, at work I'm pulling back all of the information from the user object and none of it gets updated on login.

So now I'm really confused and am going to have to dig into this deeper but in the end I'm thinking how the AD is setup is going to play a role in what information is returned.