-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Consider Enabling PKCE for Authorization Code by Default #16391
Copy link
Copy link
Closed
Labels
in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)status: duplicateA duplicate of another issueA duplicate of another issuetype: breaks-passivityA change that breaks passivity with the previous releaseA change that breaks passivity with the previous release
Metadata
Metadata
Assignees
Labels
in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)status: duplicateA duplicate of another issueA duplicate of another issuetype: breaks-passivityA change that breaks passivity with the previous releaseA change that breaks passivity with the previous release
Type
Fields
Give feedbackNo fields configured for issues without a type.
PKCE is recommended to prevent CSRF and authorization code injection attacks. We should consider enabling enabling PKCE for authorization_code flows by default to ensure we have secure defaults.
In order to ensure this goes as smoothly as possible, I think that we would need to:
NOTE: This is a breaking change, so it would need to be done with Spring Security 7.0.