XEP-0101: HTTP Authentication using Jabber Tickets

Abstract:This document defines a protocol for authenticating HTTP requests using Jabber Tickets.
Author:Richard Dobson
Copyright:© 1999 - 2014 XMPP Standards Foundation. SEE LEGAL NOTICES.
Status:Deferred
Type:Standards Track
Version:0.2
Last Updated:2004-01-18

WARNING: Consideration of this document has been Deferred by the XMPP Standards Foundation. Implementation of the protocol described herein is not recommended.


Table of Contents


1. Introduction
2. Requirements
3. Use Cases
    3.1. Client web browser window requests a Jabber Ticket Authentication protected web page
    3.2. Client requests JabberTicket
    3.3. Client replies to 401 HTTP error
    3.4. Server responds and allows or denies access to the file
4. Implementation Notes
5. Security Considerations
    5.1. Man in the middle
    5.2. Key length
    5.3. Ticket expiration
6. IANA Considerations
7. XMPP Registrar Considerations

Appendices
    A: Document Information
    B: Author Information
    C: Legal Notices
    D: Relation to XMPP
    E: Discussion Venue
    F: Requirements Conformance
    G: Notes
    H: Revision History


1. Introduction

Jabber Ticket Authentication is a method of authenticating with HTTP servers using your jabber identification.

This allows you to login to websites using your jabber address in a single sign-on fashion similar to .NET Passport, but unlike .NET Passport is not locked into a single authentication provider.

Tickets also mean the jabber ticket provider and the web server do not need to be tightly integrated for authentication to work, also because its not tightly integrated it means webmasters do not need to setup their own jabber server to provide tickets, they can use a third party provider even a central "tickets.jabber.org". Also because tickets are not tightly integrated it makes it far easier for webmasters to integrate with Jabber, it also makes web farms far more scalable and reliable.

2. Requirements

The motivations for this document are:

3. Use Cases

3.1 Client web browser window requests a Jabber Ticket Authentication protected web page

Example 1. Request for page

GET http://www.webserver.com/webpage.html HTTP/1.1

Example 2. The server responds with a 401 and WWW-Authenticate header

401 Unauthorised HTTP/1.1
WWW-Authenticate: JabberTicket realm="ticket.server.com"

The realm is the JID you need to request your JabberTicket from.

3.2 Client requests JabberTicket

Example 3. Request for ticket

<iq
    to='ticket.server.com'
    type='get'
    id='ticket1'>
  <query xmlns="http://jabber.org/protocol/ticket"/>
</iq>

Example 4. Server responds with jabber ticket

<iq
    to='user@domain.com/resource'
    from='ticket.server.com'
    type='result'
    id='ticket1'>
  <query xmlns="http://jabber.org/protocol/ticket">
    54yudvjhssa76dta6sgdst78r4sadsfjdhs...
  </query>
</iq>

The ticket is encrypted data represented as a string, the client does not need to decode it since it is passed to the webserver unaltered.

3.3 Client replies to 401 HTTP error

Example 5. Client HTTP request

GET http://www.webserver.com/webpage.html HTTP/1.1
Authorization: JabberTicket 54yudvjhssa76dta6sgdst78r4sadsfjdhs...

3.4 Server responds and allows or denies access to the file

Example 6. Server allows access

200 OK HTTP/1.1
Content-Type: text/html

Example 7. Server denies access

403 Forbidden HTTP/1.1

4. Implementation Notes

The following guidelines may assist developers.

5. Security Considerations

5.1 Man in the middle

This form of HTTP authentication is susceptable to man in the middle attack where the ticket could be captured and retransmitted by someone else, but this can be solved by using an encrypted jabber connection (e.g. HTTPS) and an HTTPS connection to the webserver.

5.2 Key length

It is recommended the encryption key length for the ticket be long enough to make it hard to crack the ticket.

5.3 Ticket expiration

It is recommended the ticket has an expiration and that it be between a few minutes and a few hours, e.g. 60 minutes.

6. IANA Considerations

The HTTP authentication scheme "JabberTicket" may need to be registered with IANA.

7. XMPP Registrar Considerations

The XMPP Registrar [1] will need to register the new namespace of "http://jabber.org/protocol/ticket".


Appendices


Appendix A: Document Information

Series: XEP
Number: 0101
Publisher: XMPP Standards Foundation
Status: Deferred
Type: Standards Track
Version: 0.2
Last Updated: 2004-01-18
Approving Body: XMPP Council
Dependencies: XMPP Core, RFC 2616, RFC 2617
Supersedes: None
Superseded By: None
Short Name: Not yet assigned
Source Control: HTML
This document in other formats: XML  PDF


Appendix B: Author Information

Richard Dobson

Email: richard@dobson-i.net
JabberID: richard@dobson-i.net


Appendix C: Legal Notices

Copyright

This XMPP Extension Protocol is copyright © 1999 - 2014 by the XMPP Standards Foundation (XSF).

Permissions

Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/> or obtained by writing to XMPP Standards Foundation, 1899 Wynkoop Street, Suite 600, Denver, CO 80202 USA).

Appendix D: Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.


Appendix E: Discussion Venue

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.

Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.

Given that this XMPP Extension Protocol normatively references IETF technologies, discussion on the <xsf-ietf@xmpp.org> list might also be appropriate.

Errata can be sent to <editor@xmpp.org>.


Appendix F: Requirements Conformance

The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".


Appendix G: Notes

1. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <http://xmpp.org/registrar/>.


Appendix H: Revision History

Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 0.2 (2004-01-18)

Expanded introduction, requirements, implementation notes, security concerns, and added server response use case. (red)

Version 0.1 (2003-06-25)

Initial version. (red)

END