Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4121

enable additionalCORSAllowedOrigins for application routes coming through openshift-ingress

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • openshift-4.12
    • Network Edge
    • False
    • None
    • False
    • Not Selected
    • Hide

      customer has publicly facing routes which has different domain than normal one for their application, but it is facing CORS error. It is working for OCP 3 for customers but not in OCP 4 seems some kind of security restriction.

      we have it for apiserver url, bu not for application urls.
      ref: https://docs.openshift.com/container-platform/4.6/security/allowing-javascript-access-api-server.html?extIdCarryOver=true&sc_cid=7013a000002pmEMAAY

      Show
      customer has publicly facing routes which has different domain than normal one for their application, but it is facing CORS error. It is working for OCP 3 for customers but not in OCP 4 seems some kind of security restriction. we have it for apiserver url, bu not for application urls. ref: https://docs.openshift.com/container-platform/4.6/security/allowing-javascript-access-api-server.html?extIdCarryOver=true&sc_cid=7013a000002pmEMAAY

      1. Proposed title of this feature request
      enable additionalCORSAllowedOrigins for application routes coming through openshift-ingress
      2. What is the nature and description of the request?
      customer has publicly facing routes which has different domain than normal one for their application, but it is facing CORS error. It is working for OCP 3 for customers but not in OCP 4 seems some kind of security restriction.
      3. Why does the customer need this? (List the business requirements here)
      most of the customers usually have publicly facing routes which has different domain than normal one so need to add some exception so that it will allow the url redirection.

      4. List any affected packages or components.
      haproxy/router/ingress

              mcurry@redhat.com Marc Curry
              rhn-support-manyayad Mahesh Nyayadhish
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: