Uploaded image for project: 'Keycloak'
  1. Keycloak
  2. KEYCLOAK-281

Origin Header from same domain confuses Keycloak

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 1.0-alpha-1
    • Fix Version/s: 1.0-beta-1
    • Component/s: None
    • Labels:
      None

      Description

      When:

      Having an app (running on agpushkeycloak-mobileqa.rhcloud.com) that is using Keycloak running on a different domain, e.g. keycloak-mobileqa.rhcloud.com.

      App is having Ember.js + REST architeture, asking for data.

      Given:

      Browser (Firefox, Chrome) adds Origin header which is the same as Host header to Ajax call to REST api.

      Then:

      Request goes through Keycloak Auth Server, which identifies this as CORS request.

      Current behavior:

      It fail unless user adds Origin to Web Origin via keycloak console.

      Expected behavior:

      Keycloak identifies Origin being same as host and does not treat request as CORS. It works out of the box.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kpiwko Karel Piwko
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: