CA Service Management

  • Private Community
 View Only

  • 1.  CORS Header issue with USS and CA Service Catalog

    Posted Jan 04, 2016 05:06 PM

    I am getting this error when trying to submit a CA Service Catalog request via USS.  It appears in the Console on the browser.

     

    Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://<SC CATALOG>:8080/usm/wpf?Node=icguinode.submitservicerequest&b2b=json&sh=8vfbPnJkPcu3L8ITJMoPcOeV%2BCs%3D&portal=true&locale=en_US. (Reason: CORS header 'Access-Control-Allow-Origin' missing).

     

    Frank Wall



  • 2.  Re: CORS Header issue with USS and CA Service Catalog

    Posted Jan 04, 2016 10:16 PM

    Hi Frank,

     

    Does this error appears when using other browsers such as Chrome or Firefox?

     

    Thanks,

    Naveen



  • 3.  Re: CORS Header issue with USS and CA Service Catalog

    Posted Jan 04, 2016 10:42 PM

    This is what I get the the IE that is part of Windows 10.

     

    SEC7120: Origin http://causs01 not found in Access-Control-Allow-Origin header.

    SCRIPT7002: XMLHttpRequest: Network Error 0x80700013, Could not complete the operation due to error 80700013. browse-catalog

    HTTP403: FORBIDDEN - The server understood the request, but is refusing to fulfill it.

    (XHR): POST - http://casc01:8080/usm/wpf?Node=icguinode.submitservicerequest&b2b=json&sh=VPZG3gIKQaJnbsGQUmfqkMJtrNo%3D&portal=true&locale=en_US



  • 4.  Re: CORS Header issue with USS and CA Service Catalog

    Broadcom Employee
    Posted Jan 05, 2016 09:41 AM

    Frank,

     

    Do you have any specific patches on Catalog/USS for this?  I believe this was addressed on Catalog as a fix/cumulative patch with some post install instructions to enable cross origin headers.

     

    _R



  • 5.  Re: CORS Header issue with USS and CA Service Catalog

    Posted Jan 05, 2016 09:53 AM

    If 14.1.02 (CP2) has been applied you can enable the CORS filter as per the following:

     

    Post Installation Steps for CA Service Catalog - CA Service Management - 14.1 - CA Technologies Documentation



  • 6.  Re: CORS Header issue with USS and CA Service Catalog

    Posted Jan 06, 2016 07:29 AM

    Regardless of having CP2 installed or not you can enable the required CORS filter in Tomcat by following this guide: http://stackoverflow.com/questions/16296145/set-cors-header-in-tomcat/18850438#18850438 Of course with CP2 you might be better off with doing it with the post-install steps.

     

    Be aware that Firefox will get a hiccup with wildcard domains so using the domain-specific configuration mentioned in the post-install steps instead of the wildcard is preferred. Also, if your Tomcat is older than 7.0.41 you need to download an additional JAR file to have the CORS filter class available for Tomcat. These are all mentioned on the link but I thought to emphasize the things I struggled with