VMware Cloud Community
KarthikeyanK
Contributor
Contributor

Vsphere Web "web client is not authenticated to vmware inventory service -null"

Hi All,

I have issue with  Vsphere Web client login. "web client is not authenticated to vmware inventory service -null"

when i am trying to log in my virtual center via web client it giving be above mentioned error. but it is working fine in VI client.

i am using :https://FQDN:9443/vsphere-client/#  able to reach the VCC but authentication only not happening i believe.

please help me one this issue.

web client login issue.PNG

Regards - karthi

7 Replies
vmroyale
Immortal
Immortal

Note: Discussion successfully moved from Community Website Help to VMware vCenter™ Server

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
Reply
0 Kudos
RanjnaAggarwal
VMware Employee
VMware Employee

Check this KB:-

i was getting the same issue and resolved with this KB

VMware KB: Repointing and reregistering VMware vCenter Server 5.1.x and components

Regards, Ranjna Aggarwal
Reply
0 Kudos
Teiva
Enthusiast
Enthusiast

hi karthi,

the way I have fixed it on my end is this way.

Note: I am using the vCenter Appliance

1) I logged on as as administrator@vsphere.local on the SSO server

2) Administration -> Single Sign-on -> Configuration

3) Clicked on "Identity Sources"

4) I added a new identify source of Type "Local OS" and named it "local os"

5) Clicked OK

6) I am not getting this error message anymore and can now see the inventory

I hope this fix works for you also.

Take care.

Teiva

Teiva
OscarDavey
Hot Shot
Hot Shot

Hello,

Have you tried the server's port? Is it OK?

Try from another workstation, too.

Hope will help.

Yours, Oscar

Reply
0 Kudos
0dje
Contributor
Contributor

Teiva,  thank you, your solution works
Brandon12313
Contributor
Contributor

Also worked for me. Thank you!

HelpeskEcutech
Contributor
Contributor

seems to me that the vsphere.local\administrators group was missing, only system-domain\administrators was there.

added this group and issue was gone.

Reply
0 Kudos