XEP-xxxx: Client Certificate Management 2.0

Abstract
TODO
Author
Florian Schmaus
Copyright
© 1999 – 2020 XMPP Standards Foundation. SEE LEGAL NOTICES.
Status

ProtoXEP

WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document is not yet an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at <http://xmpp.org/extensions/> and announced on the <standards@xmpp.org> mailing list.
Type
Standards Track
Version
0.0.1 (2019-02-XX)
Document Lifecycle
  1. Experimental
  2. Proposed
  3. Draft
  4. Final

1. Introduction

Certificate self-management for clients.

1.1 Difference from XEP-0257

Client Certificate Management for SASL EXTERNAL (XEP-0257) [1] defines similar mechanisms as this document. But this specification makes deliberately the following changes:

2. Adding a X.509 Certificate

2.1 Protocol for adding a X.509 Certificate

Example 1. Client Uploads an X.509 Certificate Signing Request.
<iq type='set'
    from='hamlet@shakespeare.lit/denmark'
    id='1'>
  <add-certificate-request xmlns='urn:xmpp:ccm2:add-cert:0'>
    <name>Mobile Client</name>
    <x509certificate-signing-request>
      MIICCTCCAXKgAwIBAgIJALhU0Id6xxwQMA0GCSqGSIb3DQEBBQUAMA4xDDAKBgNV
      BAMTA2ZvbzAeFw0wNzEyMjgyMDA1MTRaFw0wODEyMjcyMDA1MTRaMA4xDDAKBgNV
      BAMTA2ZvbzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0DPcfeJzKWLGE22p
      RMINLKr+CxqozF14DqkXkLUwGzTqYRi49yK6aebZ9ssFspTTjqa2uNpw1U32748t
      qU6bpACWHbcC+eZ/hm5KymXBhL3Vjfb/dW0xrtxjI9JRFgrgWAyxndlNZUpN2s3D
      hKDfVgpPSx/Zp8d/ubbARxqZZZkCAwEAAaNvMG0wHQYDVR0OBBYEFJWwFqmSRGcx
      YXmQfdF+XBWkeML4MD4GA1UdIwQ3MDWAFJWwFqmSRGcxYXmQfdF+XBWkeML4oRKk
      EDAOMQwwCgYDVQQDEwNmb2+CCQC4VNCHesccEDAMBgNVHRMEBTADAQH/MA0GCSqG
      SIb3DQEBBQUAA4GBAIhlUeGZ0d0msNVxYWAXg2lRsJt9INHJQTCJMmoUeTtaRjyp
      ffJtuopguNNBDn+MjrEp2/+zLNMahDYLXaTVmBf6zvY0hzB9Ih0kNTh23Fb5j+yK
      QChPXQUo0EGCaODWhfhKRNdseUozfNWOz9iTgMGw8eYNLllQRL//iAOfOr/8
    </x509certificate-signing-request>
  </add-certificate-request>
</iq>
Example 2. Server responds to an X.509 Certificate Signing Request.
<iq type='result'
    to='hamlet@shakespeare.lit/denmark'
    id='1'>
  <add-certificate-result xmlns='urn:xmpp:ccm2:add-cert:0'>
    <x509certificate>
      MIICCTCCAXKgAwIBAgIJALhU0Id6xxwQMA0GCSqGSIb3DQEBBQUAMA4xDDAKBgNV
      BAMTA2ZvbzAeFw0wNzEyMjgyMDA1MTRaFw0wODEyMjcyMDA1MTRaMA4xDDAKBgNV
      BAMTA2ZvbzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0DPcfeJzKWLGE22p
      RMINLKr+CxqozF14DqkXkLUwGzTqYRi49yK6aebZ9ssFspTTjqa2uNpw1U32748t
      qU6bpACWHbcC+eZ/hm5KymXBhL3Vjfb/dW0xrtxjI9JRFgrgWAyxndlNZUpN2s3D
      hKDfVgpPSx/Zp8d/ubbARxqZZZkCAwEAAaNvMG0wHQYDVR0OBBYEFJWwFqmSRGcx
      YXmQfdF+XBWkeML4MD4GA1UdIwQ3MDWAFJWwFqmSRGcxYXmQfdF+XBWkeML4oRKk
      EDAOMQwwCgYDVQQDEwNmb2+CCQC4VNCHesccEDAMBgNVHRMEBTADAQH/MA0GCSqG
      SIb3DQEBBQUAA4GBAIhlUeGZ0d0msNVxYWAXg2lRsJt9INHJQTCJMmoUeTtaRjyp
      ffJtuopguNNBDn+MjrEp2/+zLNMahDYLXaTVmBf6zvY0hzB9Ih0kNTh23Fb5j+yK
      QChPXQUo0EGCaODWhfhKRNdseUozfNWOz9iTgMGw8eYNLllQRL//iAOfOr/8
    </x509certificate>
  </add-certificate-result>
</iq>

2.2 Determing Support for Adding a X.509 Certificate

If the server supports adding a X.509 certificate, it MUST advertise the fact by include the feature 'urn:xmpp:ccm2:add-cert:0' in response to a Service Discovery (XEP-0030) [2] request.

3. Listing all X.509 Certificates

3.1 Protocol for listing all X.509 Certificates

Example 3. Client Requests List of X.509 Certificates
<iq type='get'
    from='hamlet@shakespeare.lit/denmark'
    id='2'>
  <list-certificates-request xmlns='urn:xmpp:ccm2:list-certs:0'/>
</iq>
Example 4. Server Sends List of Known X.509 Certificates
<iq type='result'
    to='hamlet@shakespeare.lit/denmark'
    id='2'>
  <list-of-certficiates xmlns='urn:xmpp:ccm2:list-certs:0'>
    <x509certificate last-used=''>
      <name>Mobile Client</name>
      <x509cert>
        ...
      </x509cert>
      <users>
        <resource>Phone</resource>
      </users>
    </x509certificate>
    <x509certificate last-used=''>
      <name>Laptop</name>
      <x509cert>
        ...
      </x509cert>
    </x509certificate>
    <x509certificate>
      <name>Desktop</name>
      <x509cert>
        ...
      </x509cert>
    </x509certificate>
  </list-of-certificates>
</iq>

Note that the certificate for 'Desktop' was never used, since the certificate has no last-used timestamp attribute.

3.2 Determing Support for Listing all Certificates

If the server supports listing all X.509 certificate, it MUST advertise the fact by include the feature 'urn:xmpp:ccm2:list-certs:0' in response to a Service Discovery (XEP-0030) [2] request.

4. Revoking a X.509 Certificate

4.1 Protocol for adding a X.509 Certificate

Example 5. Client revokes an X.509 Certificate
<iq type='set'
    from='hamlet@shakespeare.lit/denmark'
    id='revoke'>
  <revoke-certificate xmlns='urn:xmpp:ccm2:revoke-cert:0'>
    <fingerprint hash='TODO (needed?)'>[CERT FINGERPRINT IN HEX(?)]</name>
  </revoke-certificate>
</iq>

4.2 Determing Support for Revoking a X.509 Certificate

If the server supports adding a X.509 certificate, it MUST advertise the fact by include the feature 'urn:xmpp:ccm2:revoke-cert:0' in response to a Service Discovery (XEP-0030) [2] request.

5. Security Considerations

REQUIRED.

6. IANA Considerations

REQUIRED.

7. XMPP Registrar Considerations

REQUIRED.

8. XML Schema

REQUIRED for protocol specifications.


Appendices

Appendix A: Document Information

Series
XEP
Number
xxxx
Publisher
XMPP Standards Foundation
Status
ProtoXEP
Type
Standards Track
Version
0.0.1
Last Updated
2019-02-XX
Approving Body
XMPP Council
Dependencies
XMPP Core
Supersedes
None
Superseded By
None
Short Name
ccm2

This document in other formats: XML  PDF

Appendix B: Author Information

Florian Schmaus
Email
flo@geekplace.eu
JabberID
flo@geekplace.eu

Copyright

This XMPP Extension Protocol is copyright © 1999 – 2020 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 <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).

Visual Presentation

The HTML representation (you are looking at) is maintained by the XSF. It is based on the YAML CSS Framework, which is licensed under the terms of the CC-BY-SA 2.0 license.

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.

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. XEP-0257: Client Certificate Management for SASL EXTERNAL <https://xmpp.org/extensions/xep-0257.html>.

2. XEP-0030: Service Discovery <https://xmpp.org/extensions/xep-0030.html>.

Appendix H: Revision History

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

  1. Version 0.0.1 (2019-02-XX)

    First draft.

    fs

END