Uploaded image for project: 'Network Edge'
  1. Network Edge
  2. NE-1292

Support for the X-Azure-FDID HTTP Header

XMLWordPrintable

    • Support for the X-Azure-FDID HTTP Header
    • Product / Portfolio Work
    • OCPSTRAT-224[Azure] Route API option to reject headers w/o a valid associated value
    • 100% To Do, 0% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • None
    • None
    • None
    • 0

      Feature Overview (aka. Goal Summary)  

      Support for the X-Azure-FDID HTTP header

      Goals (aka. expected user outcomes)

      Requirements (aka. Acceptance Criteria):

      • R& D to break down the ask . Does this apply only for Azure ?
      • Design and implement API for enabling customers to secure their workloads from other front door deployed workloads.
      • Testing 
      • Documentation 
      • Tech Enablement 

       

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

       

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

       

      Out of Scope

      High-level list of items that are out of scope.  Initial completion during Refinement status.

       

      Background

      This feature is required by Azure to secure workloads exposed behind an Azure Front Door [2].
      Without that feature the workloads are accessible by other Azure customers that deployed a Front door.
       
      [1] https://issues.redhat.com/browse/RFE-3490

      [2] https://learn.microsoft.com/en-us/azure/frontdoor/origin-security?tabs=aks-nginx&pivots=front-door-standard-premium#front-door-identifier
       

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

       

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

       

      Interoperability Considerations

      Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

              Unassigned Unassigned
              mcurry@redhat.com Marc Curry
              None
              Shudi Li Shudi Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: