IBM Security Verify

 View Only
Expand all | Collapse all

ISVA high response times on every junction including the root junction

  • 1.  ISVA high response times on every junction including the root junction

    Posted Wed June 29, 2022 03:23 PM
    Hi, I have a problems with an implementation of ISVA, for some context we have 2 methods of access to the ISVA server:

    • Via internet the service is exposed via the third party proxy service.
    • Via intranet the service is accessed directly and we dont use of the third party proxy service.
    Our problem is that when the service is acceded via Internet the response times are so high even on the ISVA root junction that is just the index page with an enterprise logo (up to 50000ms).

    When I test the service via intranet I see the site responding without problems.

    Has anyone experience something similar with this?



  • 2.  RE: ISVA high response times on every junction including the root junction

    Posted Wed June 29, 2022 04:52 PM

    Gabriel,

     

    To me this sounds like a networking issue, potentially with the time that it takes for WebSEAL to send the response back to the client.  I would suggest that you enable pdweb.snoop tracing and take a look at the timestamps for the various networking operations.  This might help to explain where the 50000ms is being consumed.  The other option would be to enable packet tracing on the appliance, capture the packet trace and then use something like 'wireshark' to examine the resultant PCAP file to see what is happening on the network.

     

    I hope that this helps.

     

     

    Scott A. Exton
    Senior Software Engineer
    Chief Programmer - IBM Security Verify Access
    IBM Master Inventor

    cid4122760825*<a href=image002.png@01D85F83.85516C50">

     

     




    Original Message


  • 3.  RE: ISVA high response times on every junction including the root junction

    Posted Wed June 29, 2022 05:39 PM
    I am going to try to do the test tonight with the "pdweb.debug" and see if I can find something, I did enable the debug but cant find all the matching request and responses, I did find some extra headers but dont know if this could be causing the issue.

    • sec-fetch-user
    • sec-fetch-mode
    • sec-fetch-dest
    • sec-fetch-site
    • sec-ch-ua
    • sec-ch-ua-platform
    • sec-ch-ua-mobile
    • x-**-proxy


    ------------------------------
    Gabriel Labarrera
    ------------------------------

    Original Message