Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add document history section #10

Merged
merged 1 commit into from
Nov 13, 2024
Merged

Add document history section #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions draft-ietf-wimse-workload-identity-bcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -544,3 +544,26 @@ In this case, technically, the protected resource and workload are part of the s
## Custom assertion flows

While {{RFC7521}} and {{RFC7523}} are the proposed standards for this pattern, some authorization servers use {{RFC8693}} or a custom API for the issuance of an access token based on an existing platform identity credentials. These pattern are not recommended and prevent interoperability.

# Document History

[[ To be removed from the final specification ]]

-02

* Move scope from Kubernetes to generic workload identity platform
* Add various patterns to appendix
* Kubernetes
* Cloud providers
* SPIFFE
* CI/CD
* Add some security considerations
* Update title

-01

* Editorial updates

-00

* Adopted by the WIMSE WG
Loading