locked
WAP with ADFS pre-authentication - BUG when the cookie has specefic value RRS feed

  • Question

  • Good day,
    My WAP wiht ADFS preauthentication fail with :
    Error: Unspecified error
    (0x80004005)
    As soon as I have a Cookie Entry that look like "*{*,*}" I'm not sure where the issue is outside the fact that removing the coma will resolve the issue. (meaning that the web site will load again until the coma is readded)
    I can not find any error on the ADFS log and I'm not sure what to look for in the debug log.
    I have video and detail on this if requered.
    error detail :
    Web Application Proxy encountered an unexpected error while processing the request.
    Error: Unspecified error
    (0x80004005)
    Details:
    Transaction ID: {95c49762-5022-0001-25ee-c6952250d301}
    Session ID: {95c49762-5022-0001-25ee-c6952250d301}
    Published Application Name: wiki
    Published Application ID: 3272228f-2902-0c92-02b1-7077fb2bfca0
    Published Application External URL: https://XXXX/
    Published Backend URL: http://XXXXX.local/
    User: <Unknown>
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
    Device ID: <Not Applicable>
    Token State: NotFound
    Cookie State: NotFound
    Client Request URL: https://XXXX/favicon.ico
    Backend Request URL: <Not Applicable>
    Preauthentication Flow: <Not Applicable>
    Backend Server Authentication Mode:
    State Machine State: OuOfOrderFEHeadersWriting
    Response Code to Client: 500
    Response Message to Client: <Not Applicable>
    Client Certificate Issuer: <Not Found>
    Response Code from Backend: <Not Applicable>
    Frontend Response Location Header: <Not Applicable>
    Backend Response Location Header: <Not Applicable>
    Backend Request Http Verb: <Not Applicable>
    Client Request Http Verb: GET
    Thank you


    Tuesday, November 21, 2017 3:08 PM

All replies

  • I have the same Issue, did you happened to find any solution? :-)

    1.  I have a comma in the URL 
    2.  the other URL referer has some other special characters in the URL 


    • Edited by samd9 Tuesday, June 19, 2018 7:50 AM
    Tuesday, June 19, 2018 7:47 AM