| < draft-ietf-oauth-signed-http-request-00.txt | draft-ietf-oauth-signed-http-request-01.txt > | |||
|---|---|---|---|---|
| OAuth Working Group J. Richer, Ed. | OAuth Working Group J. Richer, Ed. | |||
| Internet-Draft The MITRE Corporation | Internet-Draft | |||
| Intended status: Experimental J. Bradley | Intended status: Experimental J. Bradley | |||
| Expires: January 22, 2015 Ping Identity | Expires: September 10, 2015 Ping Identity | |||
| H. Tschofenig | H. Tschofenig | |||
| ARM Limited | ARM Limited | |||
| July 21, 2014 | March 09, 2015 | |||
| A Method for Signing an HTTP Requests for OAuth | A Method for Signing an HTTP Requests for OAuth | |||
| draft-ietf-oauth-signed-http-request-00.txt | draft-ietf-oauth-signed-http-request-01.txt | |||
| Abstract | Abstract | |||
| This document a method for offering data origin authentication and | This document a method for offering data origin authentication and | |||
| integrity protection of HTTP requests. To convey the relevant data | integrity protection of HTTP requests. To convey the relevant data | |||
| items in the request a JSON-based encapsulation is used and the JSON | items in the request a JSON-based encapsulation is used and the JSON | |||
| Web Signature (JWS) technique is re-used. JWS offers integrity | Web Signature (JWS) technique is re-used. JWS offers integrity | |||
| protection using symmetric as well as asymmetric cryptography. | protection using symmetric as well as asymmetric cryptography. | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 1, line 37 ¶ | skipping to change at page 1, line 37 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on January 22, 2015. | This Internet-Draft will expire on September 10, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2015 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 10, line 46 ¶ | skipping to change at page 10, line 46 ¶ | |||
| The authors acknowledge the OAuth Working Group and submit this draft | The authors acknowledge the OAuth Working Group and submit this draft | |||
| for feedback and input into the ongoing work of signed HTTP requests | for feedback and input into the ongoing work of signed HTTP requests | |||
| for the interaction between clients and resource servers. | for the interaction between clients and resource servers. | |||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.1. Normative References | |||
| [I-D.ietf-jose-json-web-signature] | [I-D.ietf-jose-json-web-signature] | |||
| Jones, M., Bradley, J., and N. Sakimura, "JSON Web | Jones, M., Bradley, J., and N. Sakimura, "JSON Web | |||
| Signature (JWS)", draft-ietf-jose-json-web-signature-31 | Signature (JWS)", draft-ietf-jose-json-web-signature-41 | |||
| (work in progress), July 2014. | (work in progress), January 2015. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework", RFC | [RFC6749] Hardt, D., "The OAuth 2.0 Authorization Framework", RFC | |||
| 6749, October 2012. | 6749, October 2012. | |||
| [RFC6750] Jones, M. and D. Hardt, "The OAuth 2.0 Authorization | [RFC6750] Jones, M. and D. Hardt, "The OAuth 2.0 Authorization | |||
| Framework: Bearer Token Usage", RFC 6750, October 2012. | Framework: Bearer Token Usage", RFC 6750, October 2012. | |||
| skipping to change at page 11, line 28 ¶ | skipping to change at page 11, line 28 ¶ | |||
| [I-D.hunt-oauth-pop-architecture] | [I-D.hunt-oauth-pop-architecture] | |||
| Hunt, P., Richer, J., Mills, W., Mishra, P., and H. | Hunt, P., Richer, J., Mills, W., Mishra, P., and H. | |||
| Tschofenig, "OAuth 2.0 Proof-of-Possession (PoP) Security | Tschofenig, "OAuth 2.0 Proof-of-Possession (PoP) Security | |||
| Architecture", draft-hunt-oauth-pop-architecture-02 (work | Architecture", draft-hunt-oauth-pop-architecture-02 (work | |||
| in progress), June 2014. | in progress), June 2014. | |||
| Authors' Addresses | Authors' Addresses | |||
| Justin Richer (editor) | Justin Richer (editor) | |||
| The MITRE Corporation | ||||
| Email: jricher@mitre.org | Email: ietf@justin.richer.org | |||
| John Bradley | John Bradley | |||
| Ping Identity | Ping Identity | |||
| Email: ve7jtb@ve7jtb.com | Email: ve7jtb@ve7jtb.com | |||
| URI: http://www.thread-safe.com/ | URI: http://www.thread-safe.com/ | |||
| Hannes Tschofenig | Hannes Tschofenig | |||
| ARM Limited | ARM Limited | |||
| Austria | Austria | |||
| End of changes. 9 change blocks. | ||||
| 10 lines changed or deleted | 9 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||