Workload Identity Use Cases
draft-gilman-wimse-use-cases-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Evan Gilman , Justin Richer , Pieter Kasselman , Joseph A. Salowey | ||
| Last updated | 2024-02-29 (Latest revision 2023-08-28) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Workload identity systems like SPIFFE provide a unique set of security challenges, constraints, and possibilities that affect the larger systems they are a part of. This document seeks to collect use cases within that space, with a specific look at both the OAuth and SPIFFE technologies. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/bspk/draft-gilman-wimse-use-cases.
Authors
Evan Gilman
Justin Richer
Pieter Kasselman
Joseph A. Salowey
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)