To overcome the problem all I need to do was use the fully qualified domain name. This is because that the authentication for the second host is processed using cookies. By not using the FQDN then the appropriate cookie could not be found. A five minute solution for a problem that took days solve
Friday, June 21, 2013
LoadRunner SAP Web and Certificate problem
To overcome the problem all I need to do was use the fully qualified domain name. This is because that the authentication for the second host is processed using cookies. By not using the FQDN then the appropriate cookie could not be found. A five minute solution for a problem that took days solve
Subscribe to:
Post Comments (Atom)
2 comments:
How did you over come this issue ?i am facing a similar but for .net web application , where i have one SSL certificate with multiple DNS (SAN names). the error was "invalid common name" as vugen reads the 1st domain but not the sub domains
Hi Ravi, i am facing similar issue , but its for .net web application , where i have 1 SSL certificate with 3 SAN/DNS name, i have installed the SSL certificate which has all three DNS name but while recording using vugen its taking only 1st domain name not the other two , error was "Invalid common name"
can you pls let me know how to fix this?
Thanks,
Palani
Post a Comment