added it as a comment to issue 9025... let me know if you need any other info...

my upgrade also had the error with the authentication provider, had to hack my way back into the portal and remove the openid provider as I didn't have active directory listed...

From what I could gather from all the posts, everyone else with this issue had to uninstall the active directory provider to restore the login control. After getting back into my portal as host I wasn't able to find the AD provider under extensions, so I just deleted the OpenId provider and that seemed to restore my login control.

I haven't done a clean install of this release yet, only two upgrades of my main portal. The first upgraded failed horriably because I forgot to mark the newly created directly for the upgrade test as writable by network service

In 5.0 there is no Portal Aliases module, as such.

Therefore there should be bo module on the Site Settings page - and no entry in either ModuleControls, ModuleDefinitions or DesktopModules for a Portal Aliases module.

Portal Aliases is handled as a subcontrol of SiteSettings.

Having said that there have obviously been some issues in upgrading - which will be addressed in 5.0.1.

If you have access to your db - then remove the entry in Modules (if it exists) and then the Site Settings page should display.