Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8F43D7DB for ; Tue, 6 Nov 2012 18:34:14 +0000 (UTC) Received: (qmail 10464 invoked by uid 500); 6 Nov 2012 18:34:14 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 10443 invoked by uid 500); 6 Nov 2012 18:34:14 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 10350 invoked by uid 99); 6 Nov 2012 18:34:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Nov 2012 18:34:14 +0000 Date: Tue, 6 Nov 2012 18:34:14 +0000 (UTC) From: "Steven Tippetts (JIRA)" To: issues@cxf.apache.org Message-ID: <466160440.75539.1352226854360.JavaMail.jiratomcat@arcas> In-Reply-To: <912179661.70907.1352153652441.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CXF-4615) OAuthRequestFilter.java should ignore HTTP OPTIONS verb MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491687#comment-13491687 ] Steven Tippetts commented on CXF-4615: -------------------------------------- Thank you for your feedback. In order to make the CXF OAuth solution simple, I think you'll need to have a fix to this that doesn't involve the CORS filter or extending OAuthRequestFilter. Here's why I think this. My client is javascript in the browser and uses jQuery $.ajax to make the call to the OAuth resource server. The client provides the $.ajax call with the Authorization header information that includes the bearer token; however, for some reason jQuery first sends the OPTIONS request but without including the Authorization header. I'm guessing that this will be a problem for anyone using a javascript client. > OAuthRequestFilter.java should ignore HTTP OPTIONS verb > ------------------------------------------------------- > > Key: CXF-4615 > URL: https://issues.apache.org/jira/browse/CXF-4615 > Project: CXF > Issue Type: Bug > Components: JAX-RS Security > Affects Versions: 2.6.2, 2.7.0 > Reporter: Steven Tippetts > Priority: Critical > > In handleRequest of OAuthRequestFilter.java at line 54 something similar to the following should be added: > if (((String)m.get(Message.HTTP_REQUEST_METHOD)).equals("OPTIONS")) return null; > This will skip any HTTP OPTIONS verb requests. I'm getting the OPTIONS verb request when using an OAuth 2 javascript client. > I haven't found a way in the configuration to specify that OPTIONS requests should skip this filter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira