If you are already logged-in (that is : authenticated) with PRPC in the Designer Studio - and you use the 'Test Connectivity' button - you should have the option to test with 'current requestor' or (something like - sorry I will need to check later) 'new requestor' or 'new context'
If you use 'current requestor' PRPC sees you are already authenticated and you will then be allowed to run Activities (etc) that have the 'Requires Authentication' ticked.
The 'current requestor' also will bypass any Web Services Login Challenge ....I suspect this might be something to do with the confusion you are seeing here ?
Please do post the versions etc that Arvind asked for - we can perhaps build a simple test in-house to see if we can help out with this.
The point is am using a secured url (https) to connect to a service. Now when I do a test connectivity it fails but still it works from my application (ie it can connect to the other app). My question is why is this happening? Ideally my connector should not work if the test connectivity is failing.
On the contrary I have an unsecured url also. When I do the same (Test Connectivity) it is successful.
So has it (the failing of https in Test Connectivity) something got to do with the WS profile?
Can you private check out "Rule-Connect-SOAP", Activity : "ValidateInfrastructure" and add logging to step 5 (or second java step in the activity) which says "Test connection" in the Description and see at which step is it failing.