[ 
https://issues.apache.org/jira/browse/CXF-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421856#comment-13421856
 ] 

Sergey Beryozkin commented on CXF-4431:
---------------------------------------

Here is an update to get aligned closer to the v5 draft:
http://svn.apache.org/viewvc?rev=1365332&view=rev.

Will merge to 2.6.2-SNAPSHOT tomorrow

Summary of what I did:
- updated the normalization code
- timestamp is still passed - via an 'ext' parameter - however it would make 
sense to get the server code tolerable to the absence of it - will deal with it 
later.
- nonce is calculated based on the age of the client token, as per v5


I think it would be safe enough to resolve this JIRA without actually shipping 
a nonce implementation, at least for 2.6.2, custom NonceVerifier can alway be 
used which is a good start. We can review the option of shipping it post 2.6.2, 
once you tune it :-)

I won't have more time till 2.6.2 is out to deal with this issue - however 
please work with the snapshot and test if possible,
you may also spot some bugs there. It's quote close but a bit of tuning will be 
needed.
 
 
 

                
> Add support for OAuth2 'mac' token type
> ---------------------------------------
>
>                 Key: CXF-4431
>                 URL: https://issues.apache.org/jira/browse/CXF-4431
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS, JAX-RS Security
>    Affects Versions: 2.6.1
>            Reporter: Sasi M
>             Fix For: 2.7.0
>
>         Attachments: mac_token_nonce_checking.txt, mac_token_support.txt
>
>
> CXF currently supports only the Bearer token type. This token type is not 
> feasible for use without SSL.
> OAuth2 specs out the 'mac' token type that requires request signing for 
> authentication using the access token. The spec is described here:
> http://tools.ietf.org/html/draft-ietf-oauth-v2-http-mac-01

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to