-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Asymmetric Tokens and server issuing challenges #11521
Copy link
Copy link
Open
Labels
A-registry-authenticationArea: registry authentication and authorization (authn authz)Area: registry authentication and authorization (authn authz)S-triageStatus: This issue is waiting on initial triage.Status: This issue is waiting on initial triage.Z-asymmetric-tokenNightly: asymmetric-token authenticationNightly: asymmetric-token authentication
Metadata
Metadata
Assignees
Labels
A-registry-authenticationArea: registry authentication and authorization (authn authz)Area: registry authentication and authorization (authn authz)S-triageStatus: This issue is waiting on initial triage.Status: This issue is waiting on initial triage.Z-asymmetric-tokenNightly: asymmetric-token authenticationNightly: asymmetric-token authentication
Type
Fields
Give feedbackNo fields configured for issues without a type.
The 3231 RFC describes that servers can issue a one time challenge to better protect against token reuse. This was not implemented in #10771 and should be implement it before stabilization.