Security Certificate issues with VuGen script.

[srikant]

Hi All,

We have a web application where in i need to submit an XML data and
should get the response. For accessing the application, we need to
have the certificate installed in the machine.So the appln team
installed the .cer file in their server and they gave me .pfx file. I
installed the .pfx file in my machine and converted the .pfx file
to .pem file, put it in my script folder and used in the script.Now
the script is working well and fine and i could submit the xml data
and am getting the correct response.I am using HP Performance Center
to run the test.Now, when i try to run the script from HP Performance
Center, i am getting "Status Code 403:Access Forbidden" error. I
checked and verified that the .pem file is in the script folder in
Performance Center as well [by downloading the script to local
machine]. But the script is not working. Do i need to install the .pfx
in all the load generators?? or are there any work arounds for this??
Please let me know.This is an urgent request and i need your help in
closing this.

Best Regards,
Srikant

[Abhishek Banginwar]

runtime setting ->preferences -> winIet replay instead of winsocket (windows only)

--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en

--
Abhishek

[srikant]

Hi Abhishek,

Thanks for your reply.I tried by checking the WinInet option, but now
am getting another error "The certificate index is missing" and script
is not working. I am missing something...Please help.

On Sep 24, 4:04 am, Abhishek Banginwar <abhishek.bangin...@gmail.com>
wrote:

[Abhishek Banginwar]

forgot to mention; remove the add web certificate function.

[chaitanya bhatt]

What is the substatus of the 403 error you're seeing?

 

Below are the substatus IIS typically throws back during a 403 exception:

• 403.1 - Execute access forbidden.
• 403.2 - Read access forbidden.
• 403.3 - Write access forbidden.
• 403.4 - SSL required.
• 403.5 - SSL 128 required.
• 403.6 - IP address rejected.
• 403.7 - Client certificate required.
• 403.8 - Site access denied.
• 403.9 - Too many users.
• 403.10 - Invalid configuration.
• 403.11 - Password change.
• 403.12 - Mapper denied access.
• 403.13 - Client certificate revoked.
• 403.14 - Directory listing denied.
• 403.15 - Client Access Licenses exceeded.
• 403.16 - Client certificate is untrusted or invalid.
• 403.17 - Client certificate has expired or is not yet valid.

Identify the substatus to identify the type of exception. Your explaination tells me you have done everything correct so far.

 

Thanks

Chaitanya M Bhatt

http://www.performancecompetence.com

 

 

 

[srikant]

Thanks Chaithanya..i will check it..

On Sep 26, 12:04 pm, chaitanya bhatt <bhatt.chaita...@gmail.com>
wrote:

> What is the substatus of the 403 error you're seeing?
>
> Below are the substatus IIS typically throws back during a 403 exception:
>

>    - 403.1 - Execute access forbidden.
>    - 403.2 - Read access forbidden.
>    - 403.3 - Write access forbidden.
>    - 403.4 - SSL required.
>    - 403.5 - SSL 128 required.
>    - 403.6 - IP address rejected.
>    - 403.7 - Client certificate required.
>    - 403.8 - Site access denied.
>    - 403.9 - Too many users.
>    - 403.10 - Invalid configuration.
>    - 403.11 - Password change.
>    - 403.12 - Mapper denied access.
>    - 403.13 - Client certificate revoked.
>    - 403.14 - Directory listing denied.
>    - 403.15 - Client Access Licenses exceeded.
>    - 403.16 - Client certificate is untrusted or invalid.
>    - 403.17 - Client certificate has expired or is not yet valid.

>
> Identify the substatus to identify the type of exception. Your explaination
> tells me you have done everything correct so far.
>
> Thanks

> Chaitanya M Bhatthttp://www.performancecompetence.com

[srikant]

ok..i will try removing the web set certificate statement and run the
script. Thanks...

On Sep 26, 11:36 am, Abhishek Banginwar <abhishek.bangin...@gmail.com>
wrote: