Hello,
I recently added my vCenter to my Active Directory Domain and set the Domain to be the default identity source. I logged out of the Local Admin User, downloaded the Advanced Authentication Plug-In or whatever it's called and selected Use Windows Session Authentication and clicked login and it worked! However, when I try to manually type in my domain credentials it always tells me "INVALID CREDENTIALS". I've tried Domain\DomainName, DomainName@Domain.Com, just my DomainName, I've even gone to my DC and reset my password to make sure I was using the correct password. Can anyone point me in the direction of where I should start looking to see what this issue is?
Thanks,
Jared Keyes
Hi all,
any news here? Wen ran in exactly the same problem: Upgrade from VCVA 6.5 U3 to VCVA 6.7 U3j. Upgrade runs fine without any problems. VCVA has a computer account in AD (functional level 2016), we have configured Windows Integrated Authentification as identity source in SSO (VC with integrated PSC). With VCVA 6.5 U3 the AD based permissions are working fine, with VCVA 6.7 U3j they are not any more working, when username and password are specified explicitely, but connecting to VCVA 6.7 U3j with Windows Session Credentials is working. So the identitiy source is not broken completely. There is no firewall etc. between VCVA and AD or between the browser and VCVA. Strange...
We have opened a case for this with VMware Support.
Anyway, help from you guys is very appreciated!
Best regards,
Christian
P.S.: Thread VCSA 6.7U1 AD Login not possible anymore is IMHO discussing exactly the same issue.
Hi all,
quick update: We resolved the problem as described in After upgrade to 6.5 update 1 broken AD authentication . Obviously, the problem has something to do with the structure of the AD namespace - but what exactly is unclear. Please note that removing the VCVA from the AD and readding it doesn't affect defined permissions. So you haven't expect problems from this side.
Best regards,
Christian
I can tell you what worked for me, what i did was this rebooted the system with no network connectivity.
