Single sign-on doesn't work anymore from cms

[Pagnotta]

Dear all,

Can anyone help me...I've lost the single sign-on functionality on my CMS (SIM 5.0).

I've installed SIM5.0 two days ago and all was working fine...sunddently this afternoon single sign-on is dead... that means when I try to connect to smh on a managed server through CMS I need to enter a login password...

Do I have to regenerate a certificate and deploy it to all my managed systems ?

Thanks

Angelo

[Rich Purvis]

That is odd, are the system times off by a large amount? In other words is it possible that that the date setting on your system or systems got changed somehow? If they have it could cause your certs to look like they have expired. Or maybe they have expired, you might check and see - depending on how the certs were created you might get varying lengths of expiration.

-Rich

[Steven J. Marty_2]

FYI, I am seeing the same issue.

-Steve

[jim goodman]

You folks need to open a support case for this issue so support can track it. I have a case for the same problem and it has been escalated. The more support cases available the more info that can be collected.

- Jim

[Steven J. Marty_2]

Already done (this morning EST).

-Steve

[Steven Laux]

Was HP able to solve this issue? I am having trust issues myself after the upgrade to 5.0. I have tried issuing a new certificate and importing it on the managed servers. The cert imports fine. Still shows a trust issue, though.

Thanks,
Steve

[jim goodman]

To my knowledge no there is no fix yet. I have an escalation on this issue and there are developers are still hard at work on it.

- Jim

[Steven J. Marty_2]

I could not afford to wait for a fix. I wiped the upgraded v5.0 and did a clean installation of v5.0 and it works.

-Steve

[Steven J. Marty_2]

** UPDATE **

This worked on both my test SIM and production SIM servers for about a week. After the SIM servers were rebooted, the trusts all broke again.

Anyone else?

[Steven Laux]

Still having trust issues with a new install of 5.0. Created a new cert, added that cert to a VCRM and several VCAs. The trust is still not working. I'm out of ideas.

[Steven J. Marty_2]

Steven,

Have you opened a case? If not, can you? I think that would get the issue more attention.

-Steve

[Paul Nolette]

I am having the same issue plus lost software status. Everything was working fine yesterday, I had software status on 70+ servers then a few went to "Trust Issue" then overnight all of them did. I don't have single-sign on to any of them either. Turns out one of our IS people ran the Microsoft Security Updates yesterday afternoon. Right after it rebooted from the updates all these things seemed to stop working!
Go Microsoft!

[Kevin Kelling]

We have the same problem. Last week I took Steve's advice and reinstalled SIM 5.0 clean.

Yesterday I had over 250 trusted servers (which was a lot of work to get them all on the new certificate) and now the only servers that are still trusted are two (2) which are currently online.

There is a major problem here and we need HP to fix this. I opened a case with HP last week and it was escalalted to engineering. I told them we couldn't wait and reinstalled clean but now the problem is back.

Also some other strange behavior. If you press "View" while editing a list, it will show all the members that meet the list criteria. But if you access the same list from the list menu (bottom-left) the list contents are blank.

[Kevin Kelling]

I meant "offline" where I said "online" above.

[jim goodman]

My escalation is still moving along with the developers still capturing data. Is the only issue you folks have just the single sign on trust? or are there other problems with your installs as well?

Thanks,
Jim

[Kevin Kelling]

yes....

I noticed that at the same time the "trust issue" reared its ugly head the VMM Service stopped communicating.

This was evidenced by scores of "added a VM" and "removed a VM" messages at about 5AM this morning as well as the following error message when you try to launch the VMM console:

Communication has been lost with the VMM service.

VMM console will become accessible once the communication with the CMS is re-established.

[Steven Laux]

I had problems with upgrading from 4.2. It hosed my system lists and would not let me edit them. It also would not let me delete managed nodes from the CMS. I had to install a new, fresh SIM to fix those issues. This new install is what started my problems with the trusts.
I also have a ticket open for problems with auto-event handling. When I add multiple filters to my events, they don't work. The tech working with me verified this on his system. I have not heard anything on this for about a week.

[Steven Laux]

I referred to a "tech" in my previous. I should elaborate. This was an HP Tech that verified the issue.

[Paul Nolette]

Well I removed the Security Updates I had mentioned and it had no effect. Single sign-on and software status still doens't work. I would have bet that was it since this happened right after the updates where applied.

[jim goodman]

In my case we installed all of the security updates prior to the install of 5.0 - I wonder if we all are using the same OS win2k3sp1 and if these are all new installs as opposed to upgraded that manifested this SSO issue. I would really like to try and duplicate this in my lab.

- Jim

[Paul Nolette]

My cms is 5.0 it was installed the week 5.0 was released as an upgrade to 4.2. It's installed on a 2003 SP1 server. Everything worked great on it until yesterday and nothing beside the Security Updates changed on this server.

[Kevin Kelling]

Jim:

Our CMS is running 2003 SP1.

Originally we upgraded from SIM 4.2 to SIM 5. All security updates were current at this time.

About a week later we experienced the symptoms.

SIM was uninstalled and then reinstalled clean -- no changes to security updates.

The problem again manifested itself in about a week.

Hope this helps.

[Steven Laux]

Jim,
My SIM is running on Win2003 SP1 with no additional MS hotfixes. This is a clean SIM 5.0 install.

[jim goodman]

Ok we got 3 - win2k3sp1 so far we all have that in common.

It also doesn't fail right away but manifests itself in about 3 days to a week.

We have both upgrade from 4.2 and new installs of 5

I have a lab server with win2k3sp1 on it with HpSIM 4.2sp2 so I am going to upgrade it and see what happens.

- Jim

[Steven J. Marty_2]

I created a new CMS in my lab today. It is running Windows 2003 SP1 and I installed SIM v5.0 fresh. Everything is working with serveral monitored devices (pass-through and software statuses are OK). I rebooted the CMS a few times and it is still working.

I plan on checking it daily. Rebooting it and then checking again.

HP AET and Engineering are working on this issue. They have capture data from me also. The more individuals that open cases, the better.

-Steve