Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-9597

Goto URL with multiple query string parameters incorrectly decoded


    • Sprint:
      Sprint "Anise" 113 - Turing, Sprint "Baharat" 114 - Turing
    • Support Ticket IDs:


      OpenAM needs to be able to redirect an unauthenticated user to a specific URL after they authenticate. This URL may contain multiple query string parameters, such as "http://www.google.com/?foo=bar&hello=world". This URL it is expected to be encoded and passed into the XUI as a URL like so:


      The REST endpoint "/openam/json/authenticate" also expects to receive this URL as an encoded parameter. This is used to start the authentication process, and the goto URL provided to the authentication process will be retained throughout the lifetime of the session that will be created.

      The problem is that the encoded value passed into XUI is being decoded before it is passed to the authenticate endpoint. This is especially problematic when URLs contain multiple parameters, as it causes the URL-splitting logic to incorrectly parse the subsequent parameters of the goto URL as being additional parameters to the authenticate endpoint (unrelated to the goto URL). For example, the above would be passed in like so:


      Thus, the value for the "goto" parameter would only be "http://www.google.com/?foo=bar", and there would be another (likely ignored) parameter "hello=world" treated separately.

      The expected behavior is for the XUI to submit this goto URL encoded, like so:


      This is especially troublesome for the OAuth flow. In that case, the "authorize" endpoint redirects unauthenticated users to the XUI login page, with a URL like so:


      However when the XUI loads, it submits the goto URL it was provided to the "authenticate" endpoint without retaining the encoding, so that the authenticate endpoint only sees a goto URL with a value like so:


      The remaining, critically-important OAuth parameters are missing from the URL, so that when the authentication process completes the authorization endpoint is unable to process the request and the user can't return to their requested application (the RP) with the authorization code.


          Issue Links



              • Assignee:
                julian.kigwana@forgerock.com Julian Kigwana [X] (Inactive)
                jake.feasel Jake Feasel
                QA Assignee:
                Filip Kubáň [X] (Inactive)
              • Votes:
                1 Vote for this issue
                12 Start watching this issue


                • Created: