has anyone been able ot use the SSP feautre while usinga trusted 3rd party wildcard certificate? At least for us, the feature only works if we use the self-signed certificate. Any attempt to get to the SSP using a 3rd party cert results in "Oops - Server error" and little else. Considering this is an end-user facing site, that presents obvious problems.
So just doing a reality check: anyone out there using a 3rd party wildcard cert and getting a working SSP?
But what can be done to existing deployments to fix the issue? I too am having the problem, and have no intention of going back to a self-signed cert.
DO we have a timeline for 5.0.2?
I ask as I opened the ticket back in 5.0.0, was told it was identified, then my ticket was closed during 184.108.40.206, and now in 5.0.1 it's still not resolved ao was checking in to see if it "was just me".
Same issue here. Acropolis 220.127.116.11. Just updated to a signed cert and receive the "Oops. Server error" message too.