WIMSE Service to Service Authentication
draft-sheffer-wimse-s2s-protocol-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brian Campbell , Daniel Feldman , Joe Salowey , Arndt Schwenkschuster , Yaron Sheffer | ||
| Last updated | 2024-07-03 | ||
| Replaced by | draft-ietf-wimse-s2s-protocol | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-wimse-s2s-protocol | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The WIMSE architecture defines authentication and authorization for software workloads in a variety of runtime environments, from the most basic ones up to complex multi-service, multi-cloud, multi- tenant deployments. This document defines the simplest, atomic unit of this architecture: the protocol between two workloads that need to verify each other's identity in order to communicate securely. The scope of this protocol is a single HTTP request-and-response pair. To address the needs of different setups, we propose two protocols, one at the application level and one that makes use of trusted TLS transport. These two protocols are compatible, in the sense that a single call chain can have some calls use one protocol and some use the other. Service A can call Service B with mutual TLS authentication, while the next call from Service B to Service C would be authenticated at the application level.
Authors
Brian Campbell
Daniel Feldman
Joe Salowey
Arndt Schwenkschuster
Yaron Sheffer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)