[MS-RCMP]: Remote Certificate Mapping Protocol
Specifies the Remote Certificate Mapping Protocol, which enables servers to use a directory, database, or other technology to map the user's X.509 certificate to a security principal.
This page and associated content may be updated frequently. We recommend you subscribe to the RSS feed to receive update notifications.
Published Version
|
Date |
Protocol Revision |
Revision Class |
Downloads |
|---|---|---|---|
|
4/23/2024 |
16.0 |
Major |
Click here to download a zip file of all PDF files for Windows Protocols.
Previous Versions
|
Date |
Protocol Revision |
Revision Class |
Downloads |
|---|---|---|---|
|
6/25/2021 |
15.0 |
Major |
|
|
4/7/2021 |
14.0 |
Major |
|
|
9/12/2018 |
13.0 |
Major |
|
|
9/15/2017 |
12.0 |
Major |
|
|
6/1/2017 |
11.0 |
None |
|
|
7/14/2016 |
11.0 |
None |
|
|
10/16/2015 |
11.0 |
None |
|
|
6/30/2015 |
11.0 |
Major |
|
|
5/15/2014 |
10.0 |
None |
|
|
2/13/2014 |
10.0 |
None |
|
|
11/14/2013 |
10.0 |
None |
|
|
8/8/2013 |
10.0 |
Major |
|
|
1/31/2013 |
9.0 |
None |
|
|
10/25/2012 |
9.0 |
Major |
|
|
7/12/2012 |
8.0 |
None |
|
|
3/30/2012 |
8.0 |
None |
|
|
12/16/2011 |
8.0 |
Major |
|
|
9/23/2011 |
7.1 |
None |
|
|
6/17/2011 |
7.1 |
Minor |
|
|
5/6/2011 |
7.0 |
None |
|
|
3/25/2011 |
7.0 |
None |
|
|
2/11/2011 |
7.0 |
None |
|
|
1/7/2011 |
7.0 |
None |
|
|
11/19/2010 |
7.0 |
None |
|
|
10/8/2010 |
7.0 |
None |
|
|
8/27/2010 |
7.0 |
None |
|
|
7/16/2010 |
7.0 |
None |
|
|
6/4/2010 |
7.0 |
Major |
|
|
4/23/2010 |
6.1.2 |
Editorial |
|
|
3/12/2010 |
6.1.1 |
Editorial |
|
|
1/29/2010 |
6.1 |
Minor |
|
|
12/18/2009 |
6.0 |
Major |
|
|
11/6/2009 |
5.1.1 |
Editorial |
|
|
9/25/2009 |
5.1 |
Minor |
|
|
8/14/2009 |
5.0.1 |
Editorial |
|
|
7/2/2009 |
5.0 |
Major |
|
|
5/22/2009 |
4.0 |
Major |
|
|
4/10/2009 |
3.0.3 |
Editorial |
|
|
2/27/2009 |
3.0.2 |
Editorial |
|
|
1/16/2009 |
3.0.1 |
Editorial |
|
|
12/5/2008 |
3.0 |
Major |
|
|
10/24/2008 |
2.2.2 |
Editorial |
|
|
8/29/2008 |
2.2.1 |
Editorial |
|
|
7/25/2008 |
2.2 |
Minor |
|
|
6/20/2008 |
2.1 |
Minor |
|
|
3/14/2008 |
2.0.2 |
Editorial |
|
|
1/25/2008 |
2.0.1 |
Editorial |
|
|
10/23/2007 |
2.0 |
Major |
|
|
9/28/2007 |
1.3.3 |
Editorial |
|
|
8/10/2007 |
1.3.2 |
Editorial |
|
|
7/3/2007 |
1.3.1 |
Editorial |
|
|
6/1/2007 |
1.3 |
Minor |
|
|
5/11/2007 |
1.2 |
Minor |
|
|
4/3/2007 |
1.1 |
Minor |
|
|
3/2/2007 |
1.0 |
Major |
|
Preview Versions
From time to time, Microsoft may publish a preview, or pre-release, version of an Open Specifications technical document for community review and feedback. To submit feedback for a preview version of a technical document, please follow any instructions specified for that document. If no instructions are indicated for the document, please provide feedback by using the Open Specification Forums.
The preview period for a technical document varies. Additionally, not every technical document will be published for preview.
A preview version of this document may be available on the Windows Protocols - Preview Documents page. After the preview period, the most current version of the document is available on this page.
Development Resources
Find resources for creating interoperable solutions for Microsoft software, services, hardware, and non-Microsoft products:
Plugfests and Events, Test Tools, Development Support, and Open Specifications Dev Center.
Intellectual Property Rights Notice for Open Specifications Documentation
Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions.
Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation.
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg@microsoft.com.
License Programs. To see all of the protocols in scope under a specific license program and the associated patents, visit the Patent Map.
Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it.
Support. For questions and support, please contact dochelp@microsoft.com.