CHiLL Posted January 5, 2023 Posted January 5, 2023 (edited) I'm redoing our APC PCNS config after some issues over the Christmas break and I'm having issues configuring it to work correctly with VSphere. I've created a local account for PCNS on VSphere, specified the password and made it an administrator. I also made sure to propagate the permission to children. I've confirmed that it's propagated, as I can see the user specified in all levels of my VC structure (including individual hosts), as an Administrator and defined by the Global Permission. I've then specified those credentials (confirmed by copying and pasting from notepad) into the PCNS config, which does actually authenticate against VSphere (I can see the successful login in the Event Console). However, a minute or two later I see failed login events for the two hosts. Description: 01/05/2023, 1:55:50 PM Cannot login VSPHERE.LOCAL\PCNS@. Type: Error Date: 01/05/2023, 2:18:53 PM Task: Target: User: VSPHERE.LOCAL\APC Event Type ID: vim.event.BadUsernameSessionEvent Event Type Description: A user attempted to log in with an unknown or invalid username I'm currently quite confused why it can't connect to the individual hosts. Edited January 5, 2023 by CHiLL
psydii Posted January 6, 2023 Posted January 6, 2023 Not familiar with this myself, however I notice that in that event you have two usernames recorded: VSPHERE.LOCAL\PCNS@ and VSPHERE.LOCAL\APC is that how it is supposed to be?
CHiLL Posted January 6, 2023 Author Posted January 6, 2023 Not familiar with this myself, however I notice that in that event you have two usernames recorded: VSPHERE.LOCAL\PCNS@ and VSPHERE.LOCAL\APC is that how it is supposed to be? Sorry, that was my mistake when creating the post. I changed the usernames so I wasn't posting the actual real stuff, but wrote two different usernames by mistake. I can confirm that the usernames are actually the same (unfortunately, I can't edit the original post now).
CHiLL Posted January 17, 2023 Author Posted January 17, 2023 Bump, this is still an issue for us unfortunately. Has anyone encountered this before?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now