IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Webseal Blocked .js file.

    Posted Mon February 21, 2022 07:59 AM
      |   view attached
    I have on boarded one application in ISAM and used the Header Based Mechanism for SSO.
    Before moved to Production we have successfully tested the Login part in stage environment and its working as excepted but when application team moved their code to Production and i have done the same configuration in production as stage ISAM like created the junction and all.
    after done the configuration in Production and we tried to login the application but looks like webseal blocked some js file to reach to application getting error connection reset in the browser

    Out side the SSO application is working fine and there is no js is blocking in the browser, I have attached the both screenshot.

    Find the blocked Script:-

    https://appaccess.stc.com.sa/lmdsso/runtime-es2015.304311e26e0b02e7afd5.js

    https://appaccess.stc.com.sa/lmdsso/main-es2015.668e685a9aa13e242b7d.js

    https://appaccess.stc.com.sa/lmdsso/5-es2015.bfb91e50601e654324d7.js

    https://appaccess.stc.com.sa/lmdsso/polyfills-es2015.2a5ba7ce1548155de373.js

    https://appaccess.stc.com.sa/lmdsso/runtime-es2015.304311e26e0b02e7afd5.js

    main-es2015.668e685a9aa13e242b7d.js:1 ERROR Error: Uncaught (in promise): ChunkLoadError: Loading chunk 5 failed.

    (error: https://appaccess.stc.com.sa/lmdsso/5-es2015.bfb91e50601e654324d7.js)

    ChunkLoadError: Loading chunk 5 failed.

    (error: https://appaccess.stc.com.sa/lmdsso/5-es2015.bfb91e50601e654324d7.js)

       at Function.i.e (runtime-es2015.304311e26e0b02e7afd5.js:1:935)

       at i (main-es2015.668e685a9aa13e242b7d.js:1:1091151)

       at t.loadAndCompile (main-es2015.668e685a9aa13e242b7d.js:1:1273109)

       at t.load (main-es2015.668e685a9aa13e242b7d.js:1:1273009)

       at hn.loadModuleFactory (main-es2015.668e685a9aa13e242b7d.js:1:1470190)

       at hn.load (main-es2015.668e685a9aa13e242b7d.js:1:1469944)

       at l.project (main-es2015.668e685a9aa13e242b7d.js:1:1459494)

       at l._tryNext (main-es2015.668e685a9aa13e242b7d.js:1:188641)

       at l._next (main-es2015.668e685a9aa13e242b7d.js:1:188559)

       at l.next (main-es2015.668e685a9aa13e242b7d.js:1:443949)

       at v (polyfills-es2015.2a5ba7ce1548155de373.js:1:12579)

       at v (polyfills-es2015.2a5ba7ce1548155de373.js:1:12121)

       at polyfills-es2015.2a5ba7ce1548155de373.js:1:13393

       at a.invokeTask (polyfills-es2015.2a5ba7ce1548155de373.js:1:7689)

       at Object.onInvokeTask (main-es2015.668e685a9aa13e242b7d.js:1:1261500)

       at a.invokeTask (polyfills-es2015.2a5ba7ce1548155de373.js:1:7610)

       at s.runTask (polyfills-es2015.2a5ba7ce1548155de373.js:1:3195)

       at _ (polyfills-es2015.2a5ba7ce1548155de373.js:1:9634)

       at c.invokeTask [as invoke] (polyfills-es2015.2a5ba7ce1548155de373.js:1:8719)

       at u (polyfills-es2015.2a5ba7ce1548155de373.js:1:20298)



    Browser Console screenshot attached

    ------------------------------
    Anil Dagar
    ------------------------------


  • 2.  RE: Webseal Blocked .js file.

    Posted Mon February 21, 2022 10:39 PM
    HI
    seems connection reset is the cause of it.

    not sure why some JavaScript will get connect reset . could you check if there is any other component in front of reverse proxy causing it and its caused for each request.

    you need to check reverse proxy request.log to see if other request(other javascript)  reached reverse proxy otherwise you need to rely on network trace to find the source of the connection reset.

    thanks
    tushar

    ------------------------------
    Tushar
    Tushar
    ------------------------------

    Original Message