[
https://issues.apache.org/jira/browse/CXF-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904304#comment-13904304
]
Sergey Beryozkin edited comment on CXF-5569 at 2/18/14 5:47 PM:
----------------------------------------------------------------
Hi, can you give me a favor and explain which parameter affects the signature
calculation on the client side and is not taken into the consideration on the
server side and link to the relevant text in the OAuth1 spec ?
Thanks, Sergey
was (Author: sergey_beryozkin):
Hi, can you give me a favor and explain which parameter affects the signature
calculation on the client side which is not taken into the consideration on the
server side and link to the relevant text in the OAuth1 spec ?
Thanks, Sergey
> OAuth AbstractAuthFilter and query parameters used for signing
> --------------------------------------------------------------
>
> Key: CXF-5569
> URL: https://issues.apache.org/jira/browse/CXF-5569
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS Security
> Affects Versions: 2.7.10
> Reporter: Jason Klapste
> Priority: Minor
>
> In the AbstractAuthFilter the query (or body) parameters used for signing are
> only those included in ALLOWED_OAUTH_PARAMETERS.
> But if I'm reading the RFC correctly, it looks are though ALL parameters
> should be considered for signature generation.
> To support both backwards compatibility, can I suggest exposing the
> ALLOWED_OAUTH_PARAMETERS to subclasses (either directly or via
> getter/setters) along with a flag that can be set to automatically include
> any and all parameters?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
