Recently I was working on one project and encountered an Interesting issue related to SSO server’s SSL Cert where it was complaining about being used for a domain name other than it was registered for.
During investigation it was revealed that there are two domain names are configured with same IP. Cert was generated with alias name, hence it was complaining when we call the primary URL which was not listed in that cert.
What that meant is, let say – you have a self-signed cert for local domain “localhost” but you trying to use it for “test.nits.com” as well and both pointing to same IP address for example “127.0.0.1”.
So what is the problem here with SSO call, as this is just a warning ?
So when we try to call this HTTPS domain where name is mismatching in cert, Async call from project is getting rejected with below error, saying certificate is invalid as per validation procedures.
Recently I was working on performance testing for one of my application and came across this issue where all of my call failing in JMeter.
I started analyzing and found it was a wizard where series of calls were on same page using ASYNC Ajax calls which were complaining “The page is performing an async postback but the ScriptManager.SupportsPartialRendering property is set to false. Ensure that the property is set to true during an async postback” due to which my main POST was failing with error “Invalid postback or callback argument”.
The strange thing was all of this was working fine when run via UI. Then started reading about when this error occurs and came across one discussion on a forum where they mentioned about SupportsPartialRenderingis not supported by every browser.