Hi Danball,

I worked around the mixed-mode child portal authentication problem you mention above by copying the windowssignin.aspx and windowssignin.aspx.vb files to the child portal's folder. I created a link called Domain Login  linked to http://parent/child/windowssignin.aspx and as long as Windows Authentication was configured on the child site a new account was created.  For the most part this worked flawlessly until my upgrade to 4.5.x .  Now the only way to login/create a new account is to actually login with my DOMAIN\UserName combination. The problem we're having in my organization is we are using a Common Access Card to login to our domain. I'm patiently awaiting for the Authentication module to be revamped!

Jon

Danball, It's not just the Users table you have to contend with. Look into the aspnet_users and the aspnet_membership tables. I posted a question this morning asking for documentation identifying the relationships between these three tables. If you have any idea yourself I would be happy to hear what you know. Seems there's more here than what's documented.

As far as duplicate accounts in the Users table that problem has not presented itself.

Jon

Jon, back in town and haven't had a chance to look at anything yet (just going through a ton of email). An obvious question but did you recopy the WindowsSignin pages when you upgraded to 4.5.3? I'll have to double check but I think there may have been a very slight change in the code behind on those pages.