Symantec IGA

 View Only
  • 1.  Issue with vApp and SPS 12.8

    Posted Jun 24, 2020 08:00 AM
    Hello All,

    We are facing an issue where we are using 12.8 SPS and protecting vApp 14.3 CP1 version with Siteminder 12.8 SP1.

    Whenever traffic is sent via SPS to vApp , there is one maxConnection parameter which reaches value to 256 and then URL becomes inaccessible. At that time we are not able to access to management console of sigma portal as well.

    it works when we are using 12.52 SPS and 12.52 Siteminder. The network in which these servers are placed is same. So it should not be an issue from network's perspective. Although we are checking this factor as well as per recommendation from Broadcom support.

    Just want to know if anyone has implemented with same configuration? Are there any other suggestions ?

    Thanks,
    Shashank


  • 2.  RE: Issue with vApp and SPS 12.8

    Broadcom Employee
    Posted Jun 24, 2020 11:24 AM
    @Christopher Hackett, We believe this is a SiteMinder issue. Can you move this discussion to the SM product space?

    Thanks,
    Bill Patton​

    ------------------------------
    And, as always Perhaps there are others in the communities who have experience in doing this and we invite them to comment here also.

    Another option may be to reach out to our partner HCL Technologies to see in what way they can assist further. The Enterprise Studio team of HCL can be reached at enterprisestudio@hcl.com. https://www.hcltech.com/enterprise-studio
    ------------------------------



  • 3.  RE: Issue with vApp and SPS 12.8

    Posted Jun 24, 2020 12:12 PM
    Hello,

    We already have an issue running with support for siteminder. Just want to understand that if this has been working for any one in IGA community.

    Thanks,
    Shashank




  • 4.  RE: Issue with vApp and SPS 12.8

    Posted Jun 24, 2020 12:36 PM
    Hello,

    Just a update that this is an issue with portal , if we use the same settings to access the IDM login URL , it is not reproduced but the moment we start accessing the portal URL , this issue is reproduced.

    Thanks,
    Shashank